Semi-persistent channel state information report

ABSTRACT

A wireless device receives a DCI from a base station. The DCI comprises a power control command of an uplink shared channel, a CSI request field, a hybrid automatic repeat request process number, and a redundancy version. Validation of the DCI for an activation of a semi-persistent CSI reporting is performed based on: a radio network temporary identifier of the semi-persistent CSI reporting, the hybrid automatic repeat request process number being set to a first value, and the redundancy version being set to a second value. The semi-persistent CSI reporting indicated by the CSI request field is activated in response to the validation being achieved. A semi-persistent CSI report is transmitted, based on the activated semi-persistent CSI reporting, via the uplink shared channel with a transmission power determined based on the power control command.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/615,905, filed Jan. 10, 2018, U.S. Provisional Application No.62/626,723, filed Feb. 6, 2018, and U.S. Provisional Application No.62/613,572, filed Jan. 4, 2018, which are hereby incorporated byreference in its entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present inventionare described herein with reference to the drawings.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present disclosure.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers in a carrier group as per an aspect of anembodiment of the present disclosure.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present disclosure.

FIG. 4 is a block diagram of a base station and a wireless device as peran aspect of an embodiment of the present disclosure.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure.

FIG. 6 is an example diagram for a protocol structure withmulti-connectivity as per an aspect of an embodiment of the presentdisclosure.

FIG. 7 is an example diagram for a protocol structure with CA and DC asper an aspect of an embodiment of the present disclosure.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present disclosure.

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentdisclosure.

FIG. 10A and FIG. 10B are example diagrams for interfaces between a 5Gcore network (e.g. NGC) and base stations (e.g. gNB and eLTE eNB) as peran aspect of an embodiment of the present disclosure.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F areexample diagrams for architectures of tight interworking between 5G RAN(e.g. gNB) and LTE RAN (e.g. (e)LTE eNB) as per an aspect of anembodiment of the present disclosure.

FIG. 12A, FIG. 12B, and FIG. 12C are example diagrams for radio protocolstructures of tight interworking bearers as per an aspect of anembodiment of the present disclosure.

FIG. 13A and FIG. 13B are example diagrams for gNB deployment scenariosas per an aspect of an embodiment of the present disclosure.

FIG. 14 is an example diagram for functional split option examples ofthe centralized gNB deployment scenario as per an aspect of anembodiment of the present disclosure.

FIG. 15 is an example diagram for synchronization signal blocktransmissions as per an aspect of an embodiment of the presentdisclosure.

FIG. 16A and FIG. 16B are example diagrams of random access proceduresas per an aspect of an embodiment of the present disclosure.

FIG. 17 is an example diagram of a MAC PDU comprising a RAR as per anaspect of an embodiment of the present disclosure.

FIG. 18A, FIG. 18B and FIG. 18C are example diagrams of RAR MAC CEs asper an aspect of an embodiment of the present disclosure.

FIG. 19 is an example diagram for random access procedure whenconfigured with multiple beams as per an aspect of an embodiment of thepresent disclosure.

FIG. 20 is an example of channel state information reference signaltransmissions when configured with multiple beams as per an aspect of anembodiment of the present disclosure.

FIG. 21 is an example of channel state information reference signaltransmissions when configured with multiple beams as per an aspect of anembodiment of the present disclosure.

FIG. 22 is an example of various beam management procedures as per anaspect of an embodiment of the present disclosure.

FIG. 23A is an example diagram for downlink beam failure scenario in atransmission receiving point (TRP) as per an aspect of an embodiment ofthe present disclosure.

FIG. 23B is an example diagram for downlink beam failure scenario inmultiple TRPs as per an aspect of an embodiment of the presentdisclosure.

FIG. 24A is an example diagram for a secondary activation/deactivationmedium access control control element (MAC CE) as per an aspect of anembodiment of the present disclosure.

FIG. 24B is an example diagram for a secondary activation/deactivationMAC CE as per an aspect of an embodiment of the present disclosure.

FIG. 25A is an example diagram for timing for CSI report when activationof a secondary cell as per an aspect of an embodiment of the presentdisclosure.

FIG. 25B is an example diagram for timing for CSI report when activationof a secondary cell as per an aspect of an embodiment of the presentdisclosure.

FIG. 26 is an example diagram for downlink control information (DCI)formats as per an aspect of an embodiment of the present disclosure.

FIG. 27 is an example diagram for bandwidth part (BWP) configurations asper an aspect of an embodiment of the present disclosure.

FIG. 28 is an example diagram for BWP operation in a secondary cell asper an aspect of an embodiment of the present disclosure.

FIG. 29 is an example diagram for various CSI reporting mechanisms asper an aspect of an embodiment of the present disclosure.

FIG. 30 is an example diagram for semi-persistent CSI reportingmechanism as per an aspect of an embodiment of the present disclosure.

FIG. 31 is an example diagram for semi-persistent CSI reportingmechanism as per an aspect of an embodiment of the present disclosure.

FIG. 32 is an example diagram for semi-persistent CSI reportingmechanism as per an aspect of an embodiment of the present disclosure.

FIG. 33 is an example flowchart of semi-persistent CSI reportingmechanism as per an aspect of an embodiment of the present disclosure.

FIG. 34 is an example flowchart of semi-persistent CSI reportingmechanism as per an aspect of an embodiment of the present disclosure.

FIG. 35 is an example flowchart of semi-persistent CSI reportingmechanism as per an aspect of an embodiment of the present disclosure.

FIG. 36 is an example flowchart of beam failure recovery procedure asper an aspect of an embodiment of the present disclosure.

FIG. 37 is an example diagram of beam failure recovery procedure as peran aspect of an embodiment of the present disclosure.

FIG. 38 is an example diagram of beam failure recovery procedure as peran aspect of an embodiment of the present disclosure.

FIG. 39 is an example diagram of beam failure recovery procedure as peran aspect of an embodiment of the present disclosure.

FIG. 40 is an example diagram of beam failure recovery procedure as peran aspect of an embodiment of the present disclosure.

FIG. 41 is an example diagram of beam failure recovery procedure as peran aspect of an embodiment of the present disclosure.

FIG. 42 is an example diagram of beam failure recovery procedure as peran aspect of an embodiment of the present disclosure.

FIG. 43 is an example diagram of beam failure recovery procedure as peran aspect of an embodiment of the present disclosure.

FIG. 44 is an example diagram of beam failure recovery procedure as peran aspect of an embodiment of the present disclosure.

FIG. 45A and FIG. 45B are example diagrams of a MAC CE and a MACsubheader of activation/deactivation of SP CSI report as per an aspectof an embodiment of the present disclosure.

FIG. 46A and FIG. 46B are example diagrams of a MAC CE and a MACsubheader of activation/deactivation of SP CSI report for multipleSCells as per an aspect of an embodiment of the present disclosure.

FIG. 47 is an example diagram of a MAC CE of activation/deactivation ofSP CSI report for multiple SCells as per an aspect of an embodiment ofthe present disclosure.

FIG. 48A and FIG. 48B are example diagrams of a MAC CE and a MACsubheader of activation/deactivation and RS resource configuration of SPCSI report as per an aspect of an embodiment of the present disclosure.

FIG. 49A and FIG. 49B are example diagrams of a MAC CE and a MACsubheader of activation/deactivation and RS resource configuration of SPCSI report for multiple SCells as per an aspect of an embodiment of thepresent disclosure.

FIG. 50 is an example diagram of a MAC CE of activation/deactivation andRS resource configuration of SP CSI report for multiple SCells as per anaspect of an embodiment of the present disclosure.

FIG. 51 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 52 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 53 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 54 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 55 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 56 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 57 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 58 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 59 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 60 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 61 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 62 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 63 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 64 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present invention enable operation of carrieraggregation. Embodiments of the technology disclosed herein may beemployed in the technical field of multicarrier communication systems.More particularly, the embodiments of the technology disclosed hereinmay relate to signal transmission in a multicarrier communicationsystem.

The following Acronyms are used throughout the present disclosure:

ASIC application-specific integrated circuit

BPSK binary phase shift keying

CA carrier aggregation

CC component carrier

CDMA code division multiple access

CP cyclic prefix

CPLD complex programmable logic devices

CSI channel state information

CSS common search space

CU central unit

DC dual connectivity

DCI downlink control information

DL downlink

DU distributed unit

eMBB enhanced mobile broadband

EPC evolved packet core

E-UTRAN evolved-universal terrestrial radio access network

FDD frequency division multiplexing

FPGA field programmable gate arrays

Fs-C Fs-control plane

Fs-U Fs-user plane

gNB next generation node B

HDL hardware description languages

HARQ hybrid automatic repeat request

IE information element

LTE long term evolution

MAC media access control

MCG master cell group

MeNB master evolved node B

MIB master information block

MME mobility management entity

mMTC massive machine type communications

NAS non-access stratum

NGC next generation core

NG CP next generation control plane core

NG-C NG-control plane

NG-U NG-user plane

NR new radio

NR MAC new radio MAC

NR PHY new radio physical

NR PDCP new radio PDCP

NR RLC new radio RLC

NR RRC new radio RRC

NSSAI network slice selection assistance information

OFDM orthogonal frequency division multiplexing

PCC primary component carrier

PCell primary cell

PDCCH physical downlink control channel

PDCP packet data convergence protocol

PDU packet data unit

PHICH physical HARQ indicator channel

PHY physical

PLMN public land mobile network

PSCell primary secondary cell

pTAG primary timing advance group

PUCCH physical uplink control channel

PUSCH physical uplink shared channel

QAM quadrature amplitude modulation

QPSK quadrature phase shift keying

RA random access

RB resource blocks

RBG resource block groups

RLC radio link control

RRC radio resource control

SCC secondary component carrier

SCell secondary cell

SCG secondary cell group

SC-OFDM single carrier-OFDM

SDU service data unit

SeNB secondary evolved node B

SIB system information block

SFN system frame number

sTAGs secondary timing advance group

S-GW serving gateway

SRB signaling radio bearer

TA timing advance

TAG timing advance group

TAI tracking area identifier

TAT time alignment timer

TB transport block

TDD time division duplexing

TDMA time division multiple access

TTI transmission time interval

UE user equipment

UL uplink

UPGW user plane gateway

URLLC ultra-reliable low-latency communications

VHDL VHSIC hardware description language

Xn-C Xn-control plane

Xn-U Xn-user plane

Xx-C Xx-control plane

Xx-U Xx-user plane

Example embodiments of the invention may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but are not limited to: CDMA, OFDM,TDMA, Wavelet technologies, and/or the like. Hybrid transmissionmechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed.Various modulation schemes may be applied for signal transmission in thephysical layer. Examples of modulation schemes include, but are notlimited to: phase, amplitude, code, a combination of these, and/or thelike. An example radio transmission method may implement QAM using BPSK,QPSK, 16-QAM, 64-QAM, 256-QAM, 1024-QAM and/or the like. Physical radiotransmission may be enhanced by dynamically or semi-dynamically changingthe modulation and coding scheme depending on transmission requirementsand radio conditions.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present disclosure. As illustrated inthis example, arrow(s) in the diagram may depict a subcarrier in amulticarrier OFDM system. The OFDM system may use technology such asOFDM technology, DFTS-OFDM, SC-OFDM technology, or the like. Forexample, arrow 101 shows a subcarrier transmitting information symbols.FIG. 1 is for illustration purposes, and a typical multicarrier OFDMsystem may include more subcarriers in a carrier. For example, thenumber of subcarriers in a carrier may be in the range of 10 to 10,000subcarriers. FIG. 1 shows two guard bands 106 and 107 in a transmissionband. As illustrated in FIG. 1, guard band 106 is between subcarriers103 and subcarriers 104. The example set of subcarriers A 102 includessubcarriers 103 and subcarriers 104. FIG. 1 also illustrates an exampleset of subcarriers B 105. As illustrated, there is no guard band betweenany two subcarriers in the example set of subcarriers B 105. Carriers ina multicarrier OFDM communication system may be contiguous carriers,non-contiguous carriers, or a combination of both contiguous andnon-contiguous carriers.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers as per an aspect of an embodiment of the presentdisclosure. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 10 carriers. Carrier A 204and carrier B 205 may have the same or different timing structures.Although FIG. 2 shows two synchronized carriers, carrier A 204 andcarrier B 205 may or may not be synchronized with each other. Differentradio frame structures may be supported for FDD and TDD duplexmechanisms. FIG. 2 shows an example FDD frame timing. Downlink anduplink transmissions may be organized into radio frames 201. In thisexample, radio frame duration is 10 msec. Other frame durations, forexample, in the range of 1 to 100 msec may also be supported. In thisexample, each 10 ms radio frame 201 may be divided into ten equallysized subframes 202. Other subframe durations such as including 0.5msec, 1 msec, 2 msec, and 5 msec may also be supported. Subframe(s) maycomprise of two or more slots (e.g. slots 206 and 207). For the exampleof FDD, 10 subframes may be available for downlink transmission and 10subframes may be available for uplink transmissions in each 10 msinterval. Uplink and downlink transmissions may be separated in thefrequency domain. A slot may be 7 or 14 OFDM symbols for the samesubcarrier spacing of up to 60 kHz with normal CP. A slot may be 14 OFDMsymbols for the same subcarrier spacing higher than 60 kHz with normalCP. A slot may contain all downlink, all uplink, or a downlink part andan uplink part and/or alike. Slot aggregation may be supported, e.g.,data transmission may be scheduled to span one or multiple slots. In anexample, a mini-slot may start at an OFDM symbol in a subframe. Amini-slot may have a duration of one or more OFDM symbols. Slot(s) mayinclude a plurality of OFDM symbols 203. The number of OFDM symbols 203in a slot 206 may depend on the cyclic prefix length and subcarrierspacing.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present disclosure. The resource grid structure intime 304 and frequency 305 is illustrated in FIG. 3. The quantity ofdownlink subcarriers or RBs may depend, at least in part, on thedownlink transmission bandwidth 306 configured in the cell. The smallestradio resource unit may be called a resource element (e.g. 301).Resource elements may be grouped into resource blocks (e.g. 302).Resource blocks may be grouped into larger radio resources calledResource Block Groups (RBG) (e.g. 303). The transmitted signal in slot206 may be described by one or several resource grids of a plurality ofsubcarriers and a plurality of OFDM symbols. Resource blocks may be usedto describe the mapping of certain physical channels to resourceelements. Other pre-defined groupings of physical resource elements maybe implemented in the system depending on the radio technology. Forexample, 24 subcarriers may be grouped as a radio block for a durationof 5 msec. In an illustrative example, a resource block may correspondto one slot in the time domain and 180 kHz in the frequency domain (for15 KHz subcarrier bandwidth and 12 subcarriers).

In an example embodiment, multiple numerologies may be supported. In anexample, a numerology may be derived by scaling a basic subcarrierspacing by an integer N. In an example, scalable numerology may allow atleast from 15 kHz to 480 kHz subcarrier spacing. The numerology with 15kHz and scaled numerology with different subcarrier spacing with thesame CP overhead may align at a symbol boundary every 1 ms in a NRcarrier.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure. FIG. 5A shows an example uplink physicalchannel. The baseband signal representing the physical uplink sharedchannel may perform the following processes. These functions areillustrated as examples and it is anticipated that other mechanisms maybe implemented in various embodiments. The functions may comprisescrambling, modulation of scrambled bits to generate complex-valuedsymbols, mapping of the complex-valued modulation symbols onto one orseveral transmission layers, transform precoding to generatecomplex-valued symbols, precoding of the complex-valued symbols, mappingof precoded complex-valued symbols to resource elements, generation ofcomplex-valued time-domain DFTS-OFDM/SC-FDMA signal for an antenna port,and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued DFTS-OFDM/SC-FDMA baseband signal for an antenna portand/or the complex-valued PRACH baseband signal is shown in FIG. 5B.Filtering may be employed prior to transmission.

An example structure for Downlink Transmissions is shown in FIG. 5C. Thebaseband signal representing a downlink physical channel may perform thefollowing processes. These functions are illustrated as examples and itis anticipated that other mechanisms may be implemented in variousembodiments. The functions include scrambling of coded bits in codewordsto be transmitted on a physical channel; modulation of scrambled bits togenerate complex-valued modulation symbols; mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers; precoding of the complex-valued modulation symbols on a layerfor transmission on the antenna ports; mapping of complex-valuedmodulation symbols for an antenna port to resource elements; generationof complex-valued time-domain OFDM signal for an antenna port, and/orthe like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for an antenna port is shown in FIG.5D. Filtering may be employed prior to transmission.

FIG. 4 is an example block diagram of a base station 401 and a wirelessdevice 406, as per an aspect of an embodiment of the present disclosure.A communication network 400 may include at least one base station 401and at least one wireless device 406. The base station 401 may includeat least one communication interface 402, at least one processor 403,and at least one set of program code instructions 405 stored innon-transitory memory 404 and executable by the at least one processor403. The wireless device 406 may include at least one communicationinterface 407, at least one processor 408, and at least one set ofprogram code instructions 410 stored in non-transitory memory 409 andexecutable by the at least one processor 408. Communication interface402 in base station 401 may be configured to engage in communicationwith communication interface 407 in wireless device 406 via acommunication path that includes at least one wireless link 411.Wireless link 411 may be a bi-directional link. Communication interface407 in wireless device 406 may also be configured to engage in acommunication with communication interface 402 in base station 401. Basestation 401 and wireless device 406 may be configured to send andreceive data over wireless link 411 using multiple frequency carriers.According to some of the various aspects of embodiments, transceiver(s)may be employed. A transceiver is a device that includes both atransmitter and receiver. Transceivers may be employed in devices suchas wireless devices, base stations, relay nodes, and/or the like.Example embodiments for radio technology implemented in communicationinterface 402, 407 and wireless link 411 are illustrated are FIG. 1,FIG. 2, FIG. 3, FIG. 5, and associated text.

An interface may be a hardware interface, a firmware interface, asoftware interface, and/or a combination thereof. The hardware interfacemay include connectors, wires, electronic devices such as drivers,amplifiers, and/or the like. A software interface may include codestored in a memory device to implement protocol(s), protocol layers,communication drivers, device drivers, combinations thereof, and/or thelike. A firmware interface may include a combination of embeddedhardware and code stored in and/or in communication with a memory deviceto implement connections, electronic device operations, protocol(s),protocol layers, communication drivers, device drivers, hardwareoperations, combinations thereof, and/or the like.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics inthe device, whether the device is in an operational or non-operationalstate.

According to some of the various aspects of embodiments, a 5G networkmay include a multitude of base stations, providing a user plane NRPDCP/NR RLC/NR MAC/NR PHY and control plane (NR RRC) protocolterminations towards the wireless device. The base station(s) may beinterconnected with other base station(s) (e.g. employing an Xninterface). The base stations may also be connected employing, forexample, an NG interface to an NGC. FIG. 10A and FIG. 10B are examplediagrams for interfaces between a 5G core network (e.g. NGC) and basestations (e.g. gNB and eLTE eNB) as per an aspect of an embodiment ofthe present disclosure. For example, the base stations may beinterconnected to the NGC control plane (e.g. NG CP) employing the NG-Cinterface and to the NGC user plane (e.g. UPGW) employing the NG-Uinterface. The NG interface may support a many-to-many relation between5G core networks and base stations.

A base station may include many sectors for example: 1, 2, 3, 4, or 6sectors. A base station may include many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At RRC connectionestablishment/re-establishment/handover, one serving cell may providethe NAS (non-access stratum) mobility information (e.g. TAI), and at RRCconnection re-establishment/handover, one serving cell may provide thesecurity input. This cell may be referred to as the Primary Cell(PCell). In the downlink, the carrier corresponding to the PCell may bethe Downlink Primary Component Carrier (DL PCC), while in the uplink, itmay be the Uplink Primary Component Carrier (UL PCC). Depending onwireless device capabilities, Secondary Cells (SCells) may be configuredto form together with the PCell a set of serving cells. In the downlink,the carrier corresponding to an SCell may be a Downlink SecondaryComponent Carrier (DL SCC), while in the uplink, it may be an UplinkSecondary Component Carrier (UL SCC). An SCell may or may not have anuplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to only one cell. The cell ID or Cell index mayalso identify the downlink carrier or uplink carrier of the cell(depending on the context it is used). In the specification, cell ID maybe equally referred to a carrier ID, and cell index may be referred tocarrier index. In implementation, the physical cell ID or cell index maybe assigned to a cell. A cell ID may be determined using asynchronization signal transmitted on a downlink carrier. A cell indexmay be determined using RRC messages. For example, when thespecification refers to a first physical cell ID for a first downlinkcarrier, the specification may mean the first physical cell ID is for acell comprising the first downlink carrier. The same concept may applyto, for example, carrier activation. When the specification indicatesthat a first carrier is activated, the specification may equally meanthat the cell comprising the first carrier is activated.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, traffic load, initial systemset up, packet sizes, traffic characteristics, a combination of theabove, and/or the like. When the one or more criteria are met, variousexample embodiments may be applied. Therefore, it may be possible toimplement example embodiments that selectively implement disclosedprotocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices may support multiple technologies, and/or multiple releases ofthe same technology. Wireless devices may have some specificcapability(ies) depending on its wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE or 5G releasewith a given capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of wireless devices in a coveragearea that may not comply with the disclosed methods, for example,because those wireless devices perform based on older releases of LTE or5G technology.

FIG. 6 and FIG. 7 are example diagrams for protocol structure with CAand multi-connectivity as per an aspect of an embodiment of the presentdisclosure. NR may support multi-connectivity operation whereby amultiple RX/TX UE in RRC_CONNECTED may be configured to utilize radioresources provided by multiple schedulers located in multiple gNBsconnected via a non-ideal or ideal backhaul over the Xn interface. gNBsinvolved in multi-connectivity for a certain UE may assume two differentroles: a gNB may either act as a master gNB or as a secondary gNB. Inmulti-connectivity, a UE may be connected to one master gNB and one ormore secondary gNBs. FIG. 7 illustrates one example structure for the UEside MAC entities when a Master Cell Group (MCG) and a Secondary CellGroup (SCG) are configured, and it may not restrict implementation.Media Broadcast Multicast Service (MBMS) reception is not shown in thisfigure for simplicity.

In multi-connectivity, the radio protocol architecture that a particularbearer uses may depend on how the bearer is setup. Three examples ofbearers, including, an MCG bearer, an SCG bearer and a split bearer asshown in FIG. 6. NR RRC may be located in master gNB and SRBs may beconfigured as an MCG bearer type and may use the radio resources of themaster gNB. Multi-connectivity may also be described as having at leastone bearer configured to use radio resources provided by the secondarygNB. Multi-connectivity may or may not be configured/implemented inexample embodiments of the disclosure.

In the case of multi-connectivity, the UE may be configured withmultiple NR MAC entities: one NR MAC entity for master gNB, and other NRMAC entities for secondary gNBs. In multi-connectivity, the configuredset of serving cells for a UE may comprise of two subsets: the MasterCell Group (MCG) containing the serving cells of the master gNB, and theSecondary Cell Groups (SCGs) containing the serving cells of thesecondary gNBs. For a SCG, one or more of the following may be applied:at least one cell in the SCG has a configured UL CC and one of them,named PSCell (or PCell of SCG, or sometimes called PCell), is configuredwith PUCCH resources; when the SCG is configured, there may be at leastone SCG bearer or one Split bearer; upon detection of a physical layerproblem or a random access problem on a PSCell, or the maximum number ofNR RLC retransmissions has been reached associated with the SCG, or upondetection of an access problem on a PSCell during a SCG addition or aSCG change: a RRC connection re-establishment procedure may not betriggered, UL transmissions towards cells of the SCG are stopped, amaster gNB may be informed by the UE of a SCG failure type, for splitbearer, the DL data transfer over the master gNB is maintained; the NRRLC AM bearer may be configured for the split bearer; like PCell, PSCellmay not be de-activated; PSCell may be changed with a SCG change (e.g.with security key change and a RACH procedure); and/or a direct bearertype change between a Split bearer and a SCG bearer or simultaneousconfiguration of a SCG and a Split bearer may or may not supported.

With respect to the interaction between a master gNB and secondary gNBsfor multi-connectivity, one or more of the following principles may beapplied: the master gNB may maintain the RRM measurement configurationof the UE and may, (e.g., based on received measurement reports ortraffic conditions or bearer types), decide to ask a secondary gNB toprovide additional resources (serving cells) for a UE; upon receiving arequest from the master gNB, a secondary gNB may create a container thatmay result in the configuration of additional serving cells for the UE(or decide that it has no resource available to do so); for UEcapability coordination, the master gNB may provide (part of) the ASconfiguration and the UE capabilities to the secondary gNB; the mastergNB and the secondary gNB may exchange information about a UEconfiguration by employing of NR RRC containers (inter-node messages)carried in Xn messages; the secondary gNB may initiate a reconfigurationof its existing serving cells (e.g., PUCCH towards the secondary gNB);the secondary gNB may decide which cell is the PSCell within the SCG;the master gNB may or may not change the content of the NR RRCconfiguration provided by the secondary gNB; in the case of a SCGaddition and a SCG SCell addition, the master gNB may provide the latestmeasurement results for the SCG cell(s); both a master gNB and secondarygNBs may know the SFN and subframe offset of each other by OAM, (e.g.,for the purpose of DRX alignment and identification of a measurementgap). In an example, when adding a new SCG SCell, dedicated NR RRCsignaling may be used for sending required system information of thecell as for CA, except for the SFN acquired from a MIB of the PSCell ofa SCG.

In an example, serving cells may be grouped in a TA group (TAG). Servingcells in one TAG may use the same timing reference. For a given TAG,user equipment (UE) may use at least one downlink carrier as a timingreference. For a given TAG, a UE may synchronize uplink subframe andframe transmission timing of uplink carriers belonging to the same TAG.In an example, serving cells having an uplink to which the same TAapplies may correspond to serving cells hosted by the same receiver. AUE supporting multiple TAs may support two or more TA groups. One TAgroup may contain the PCell and may be called a primary TAG (pTAG). In amultiple TAG configuration, at least one TA group may not contain thePCell and may be called a secondary TAG (sTAG). In an example, carrierswithin the same TA group may use the same TA value and/or the sametiming reference. When DC is configured, cells belonging to a cell group(MCG or SCG) may be grouped into multiple TAGs including a pTAG and oneor more sTAGs.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present disclosure. In Example 1, pTAG comprisesPCell, and an sTAG comprises SCell1. In Example 2, a pTAG comprises aPCell and SCell1, and an sTAG comprises SCell2 and SCell3. In Example 3,pTAG comprises PCell and SCell1, and an sTAG1 includes SCell2 andSCell3, and sTAG2 comprises SCell4. Up to four TAGs may be supported ina cell group (MCG or SCG) and other example TAG configurations may alsobe provided. In various examples in this disclosure, example mechanismsare described for a pTAG and an sTAG. Some of the example mechanisms maybe applied to configurations with multiple sTAGs.

In an example, an eNB may initiate an RA procedure via a PDCCH order foran activated SCell. This PDCCH order may be sent on a scheduling cell ofthis SCell. When cross carrier scheduling is configured for a cell, thescheduling cell may be different than the cell that is employed forpreamble transmission, and the PDCCH order may include an SCell index.At least a non-contention based RA procedure may be supported forSCell(s) assigned to sTAG(s).

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentdisclosure. An eNB transmits an activation command 900 to activate anSCell. A preamble 902 (Msg1) may be sent by a UE in response to a PDCCHorder 901 on an SCell belonging to an sTAG. In an example embodiment,preamble transmission for SCells may be controlled by the network usingPDCCH format 1A. Msg2 message 903 (RAR: random access response) inresponse to the preamble transmission on the SCell may be addressed toRA-RNTI in a PCell common search space (CSS). Uplink packets 904 may betransmitted on the SCell in which the preamble was transmitted.

According to some of the various aspects of embodiments, initial timingalignment may be achieved through a random access procedure. This mayinvolve a UE transmitting a random access preamble and an eNB respondingwith an initial TA command NTA (amount of timing advance) within arandom access response window. The start of the random access preamblemay be aligned with the start of a corresponding uplink subframe at theUE assuming NTA=0. The eNB may estimate the uplink timing from therandom access preamble transmitted by the UE. The TA command may bederived by the eNB based on the estimation of the difference between thedesired UL timing and the actual UL timing. The UE may determine theinitial uplink transmission timing relative to the correspondingdownlink of the sTAG on which the preamble is transmitted.

The mapping of a serving cell to a TAG may be configured by a servingeNB with RRC signaling. The mechanism for TAG configuration andreconfiguration may be based on RRC signaling. According to some of thevarious aspects of embodiments, when an eNB performs an SCell additionconfiguration, the related TAG configuration may be configured for theSCell. In an example embodiment, an eNB may modify the TAG configurationof an SCell by removing (releasing) the SCell and adding(configuring) anew SCell (with the same physical cell ID and frequency) with an updatedTAG ID. The new SCell with the updated TAG ID may initially be inactivesubsequent to being assigned the updated TAG ID. The eNB may activatethe updated new SCell and start scheduling packets on the activatedSCell. In an example implementation, it may not be possible to changethe TAG associated with an SCell, but rather, the SCell may need to beremoved and a new SCell may need to be added with another TAG. Forexample, if there is a need to move an SCell from an sTAG to a pTAG, atleast one RRC message, for example, at least one RRC reconfigurationmessage, may be send to the UE to reconfigure TAG configurations byreleasing the SCell and then configuring the SCell as a part of the pTAG(when an SCell is added/configured without a TAG index, the SCell may beexplicitly assigned to the pTAG). The PCell may not change its TA groupand may be a member of the pTAG.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g. to establish, modify and/or release RBs,to perform handover, to setup, modify, and/or release measurements, toadd, modify, and/or release SCells). If the received RRC ConnectionReconfiguration message includes the sCellToReleaseList, the UE mayperform an SCell release. If the received RRC Connection Reconfigurationmessage includes the sCellToAddModList, the UE may perform SCelladditions or modification.

In LTE Release-10 and Release-11 CA, a PUCCH is only transmitted on thePCell (PSCell) to an eNB. In LTE-Release 12 and earlier, a UE maytransmit PUCCH information on one cell (PCell or PSCell) to a given eNB.

As the number of CA capable UEs and the number of aggregated carriersincrease, the number of PUCCHs and also the PUCCH payload size mayincrease. Accommodating the PUCCH transmissions on the PCell may lead toa high PUCCH load on the PCell. A PUCCH on an SCell may be introduced tooffload the PUCCH resource from the PCell. More than one PUCCH may beconfigured for example, a PUCCH on a PCell and another PUCCH on anSCell. In the example embodiments, one, two or more cells may beconfigured with PUCCH resources for transmitting CSI/ACK/NACK to a basestation. Cells may be grouped into multiple PUCCH groups, and one ormore cell within a group may be configured with a PUCCH. In an exampleconfiguration, one SCell may belong to one PUCCH group. SCells with aconfigured PUCCH transmitted to a base station may be called a PUCCHSCell, and a cell group with a common PUCCH resource transmitted to thesame base station may be called a PUCCH group.

In an example embodiment, a MAC entity may have a configurable timertimeAlignmentTimer per TAG. The timeAlignmentTimer may be used tocontrol how long the MAC entity considers the Serving Cells belonging tothe associated TAG to be uplink time aligned. The MAC entity may, when aTiming Advance Command MAC control element is received, apply the TimingAdvance Command for the indicated TAG; start or restart thetimeAlignmentTimer associated with the indicated TAG. The MAC entitymay, when a Timing Advance Command is received in a Random AccessResponse message for a serving cell belonging to a TAG and/or if theRandom Access Preamble was not selected by the MAC entity, apply theTiming Advance Command for this TAG and start or restart thetimeAlignmentTimer associated with this TAG. Otherwise, if thetimeAlignmentTimer associated with this TAG is not running, the TimingAdvance Command for this TAG may be applied and the timeAlignmentTimerassociated with this TAG started. When the contention resolution isconsidered not successful, a timeAlignmentTimer associated with this TAGmay be stopped. Otherwise, the MAC entity may ignore the received TimingAdvance Command.

In example embodiments, a timer is running once it is started, until itis stopped or until it expires; otherwise it may not be running. A timercan be started if it is not running or restarted if it is running. Forexample, a timer may be started or restarted from its initial value.

Example embodiments of the disclosure may enable operation ofmulti-carrier communications. Other example embodiments may comprise anon-transitory tangible computer readable media comprising instructionsexecutable by one or more processors to cause operation of multi-carriercommunications. Yet other example embodiments may comprise an article ofmanufacture that comprises a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g. wirelesscommunicator, UE, base station, etc.) to enable operation ofmulti-carrier communications. The device may include processors, memory,interfaces, and/or the like. Other example embodiments may comprisecommunication networks comprising devices such as base stations,wireless devices (or user equipment: UE), servers, switches, antennas,and/or the like.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F areexample diagrams for architectures of tight interworking between 5G RANand LTE RAN as per an aspect of an embodiment of the present disclosure.The tight interworking may enable a multiple RX/TX UE in RRC_CONNECTEDto be configured to utilize radio resources provided by two schedulerslocated in two base stations (e.g. (e)LTE eNB and gNB) connected via anon-ideal or ideal backhaul over the Xx interface between LTE eNB andgNB or the Xn interface between eLTE eNB and gNB. Base stations involvedin tight interworking for a certain UE may assume two different roles: abase station may either act as a master base station or as a secondarybase station. In tight interworking, a UE may be connected to one masterbase station and one secondary base station. Mechanisms implemented intight interworking may be extended to cover more than two base stations.

In FIG. 11A and FIG. 11B, a master base station may be an LTE eNB, whichmay be connected to EPC nodes (e.g. to an MME via the S1-C interface andto an S-GW via the S1-U interface), and a secondary base station may bea gNB, which may be a non-standalone node having a control planeconnection via an Xx-C interface to an LTE eNB. In the tightinterworking architecture of FIG. 11A, a user plane for a gNB may beconnected to an S-GW through an LTE eNB via an Xx-U interface betweenLTE eNB and gNB and an S1-U interface between LTE eNB and S-GW. In thearchitecture of FIG. 11B, a user plane for a gNB may be connecteddirectly to an S-GW via an S1-U interface between gNB and S-GW.

In FIG. 11C and FIG. 11D, a master base station may be a gNB, which maybe connected to NGC nodes (e.g. to a control plane core node via theNG-C interface and to a user plane core node via the NG-U interface),and a secondary base station may be an eLTE eNB, which may be anon-standalone node having a control plane connection via an Xn-Cinterface to a gNB. In the tight interworking architecture of FIG. 11C,a user plane for an eLTE eNB may be connected to a user plane core nodethrough a gNB via an Xn-U interface between eLTE eNB and gNB and an NG-Uinterface between gNB and user plane core node. In the architecture ofFIG. 11D, a user plane for an eLTE eNB may be connected directly to auser plane core node via an NG-U interface between eLTE eNB and userplane core node.

In FIG. 11E and FIG. 11F, a master base station may be an eLTE eNB,which may be connected to NGC nodes (e.g. to a control plane core nodevia the NG-C interface and to a user plane core node via the NG-Uinterface), and a secondary base station may be a gNB, which may be anon-standalone node having a control plane connection via an Xn-Cinterface to an eLTE eNB. In the tight interworking architecture of FIG.11E, a user plane for a gNB may be connected to a user plane core nodethrough an eLTE eNB via an Xn-U interface between eLTE eNB and gNB andan NG-U interface between eLTE eNB and user plane core node. In thearchitecture of FIG. 11F, a user plane for a gNB may be connecteddirectly to a user plane core node via an NG-U interface between gNB anduser plane core node.

FIG. 12A, FIG. 12B, and FIG. 12C are example diagrams for radio protocolstructures of tight interworking bearers as per an aspect of anembodiment of the present disclosure. In FIG. 12A, an LTE eNB may be amaster base station, and a gNB may be a secondary base station. In FIG.12B, a gNB may be a master base station, and an eLTE eNB may be asecondary base station. In FIG. 12C, an eLTE eNB may be a master basestation, and a gNB may be a secondary base station. In 5G network, theradio protocol architecture that a particular bearer uses may depend onhow the bearer is setup. Three example bearers including an MCG bearer,an SCG bearer, and a split bearer as shown in FIG. 12A, FIG. 12B, andFIG. 12C. NR RRC may be located in master base station, and SRBs may beconfigured as an MCG bearer type and may use the radio resources of themaster base station. Tight interworking may also be described as havingat least one bearer configured to use radio resources provided by thesecondary base station. Tight interworking may or may not beconfigured/implemented in example embodiments of the disclosure.

In the case of tight interworking, the UE may be configured with two MACentities: one MAC entity for master base station, and one MAC entity forsecondary base station. In tight interworking, the configured set ofserving cells for a UE may comprise of two subsets: the Master CellGroup (MCG) containing the serving cells of the master base station, andthe Secondary Cell Group (SCG) containing the serving cells of thesecondary base station. For a SCG, one or more of the following may beapplied: at least one cell in the SCG has a configured UL CC and one ofthem, named PSCell (or PCell of SCG, or sometimes called PCell), isconfigured with PUCCH resources; when the SCG is configured, there maybe at least one SCG bearer or one split bearer; upon detection of aphysical layer problem or a random access problem on a PSCell, or themaximum number of (NR) RLC retransmissions has been reached associatedwith the SCG, or upon detection of an access problem on a PSCell duringa SCG addition or a SCG change: a RRC connection re-establishmentprocedure may not be triggered, UL transmissions towards cells of theSCG are stopped, a master base station may be informed by the UE of aSCG failure type, for split bearer, the DL data transfer over the masterbase station is maintained; the RLC AM bearer may be configured for thesplit bearer; like PCell, PSCell may not be de-activated; PSCell may bechanged with a SCG change (e.g. with security key change and a RACHprocedure); and/or neither a direct bearer type change between a Splitbearer and a SCG bearer nor simultaneous configuration of a SCG and aSplit bearer are supported.

With respect to the interaction between a master base station and asecondary base station, one or more of the following principles may beapplied: the master base station may maintain the RRM measurementconfiguration of the UE and may, (e.g., based on received measurementreports, traffic conditions, or bearer types), decide to ask a secondarybase station to provide additional resources (serving cells) for a UE;upon receiving a request from the master base station, a secondary basestation may create a container that may result in the configuration ofadditional serving cells for the UE (or decide that it has no resourceavailable to do so); for UE capability coordination, the master basestation may provide (part of) the AS configuration and the UEcapabilities to the secondary base station; the master base station andthe secondary base station may exchange information about a UEconfiguration by employing of RRC containers (inter-node messages)carried in Xn or Xx messages; the secondary base station may initiate areconfiguration of its existing serving cells (e.g., PUCCH towards thesecondary base station); the secondary base station may decide whichcell is the PSCell within the SCG; the master base station may notchange the content of the RRC configuration provided by the secondarybase station; in the case of a SCG addition and a SCG SCell addition,the master base station may provide the latest measurement results forthe SCG cell(s); both a master base station and a secondary base stationmay know the SFN and subframe offset of each other by OAM, (e.g., forthe purpose of DRX alignment and identification of a measurement gap).In an example, when adding a new SCG SCell, dedicated RRC signaling maybe used for sending required system information of the cell as for CA,except for the SFN acquired from a MIB of the PSCell of a SCG.

FIG. 13A and FIG. 13B are example diagrams for gNB deployment scenariosas per an aspect of an embodiment of the present disclosure. In thenon-centralized deployment scenario in FIG. 13A, the full protocol stack(e.g. NR RRC, NR PDCP, NR RLC, NR MAC, and NR PHY) may be supported atone node. In the centralized deployment scenario in FIG. 13B, upperlayers of gNB may be located in a Central Unit (CU), and lower layers ofgNB may be located in Distributed Units (DU). The CU-DU interface (e.g.Fs interface) connecting CU and DU may be ideal or non-ideal. Fs-C mayprovide a control plane connection over Fs interface, and Fs-U mayprovide a user plane connection over Fs interface. In the centralizeddeployment, different functional split options between CU and DUs may bepossible by locating different protocol layers (RAN functions) in CU andDU. The functional split may support flexibility to move RAN functionsbetween CU and DU depending on service requirements and/or networkenvironments. The functional split option may change during operationafter Fs interface setup procedure, or may change only in Fs setupprocedure (i.e. static during operation after Fs setup procedure).

FIG. 14 is an example diagram for different functional split optionexamples of the centralized gNB deployment scenario as per an aspect ofan embodiment of the present disclosure. In the split option example 1,an NR RRC may be in CU, and NR PDCP, NR RLC, NR MAC, NR PHY, and RF maybe in DU. In the split option example 2, an NR RRC and NR PDCP may be inCU, and NR RLC, NR MAC, NR PHY, and RF may be in DU. In the split optionexample 3, an NR RRC, NR PDCP, and partial function of NR RLC may be inCU, and the other partial function of NR RLC, NR MAC, NR PHY, and RF maybe in DU. In the split option example 4, an NR RRC, NR PDCP, and NR RLCmay be in CU, and NR MAC, NR PHY, and RF may be in DU. In the splitoption example 5, an NR RRC, NR PDCP, NR RLC, and partial function of NRMAC may be in CU, and the other partial function of NR MAC, NR PHY, andRF may be in DU. In the split option example 6, an NR RRC, NR PDCP, NRRLC, and NR MAC may be in CU, and NR PHY and RF may be in DU. In thesplit option example 7, an NR RRC, NR PDCP, NR RLC, NR MAC, and partialfunction of NR PHY may be in CU, and the other partial function of NRPHY and RF may be in DU. In the split option example 8, an NR RRC, NRPDCP, NR RLC, NR MAC, and NR PHY may be in CU, and RF may be in DU.

The functional split may be configured per CU, per DU, per UE, perbearer, per slice, or with other granularities. In per CU split, a CUmay have a fixed split, and DUs may be configured to match the splitoption of CU. In per DU split, a DU may be configured with a differentsplit, and a CU may provide different split options for different DUs.In per UE split, a gNB (CU and DU) may provide different split optionsfor different UEs. In per bearer split, different split options may beutilized for different bearer types. In per slice splice, differentsplit options may be applied for different slices.

In an example embodiment, the new radio access network (new RAN) maysupport different network slices, which may allow differentiatedtreatment customized to support different service requirements with endto end scope. The new RAN may provide a differentiated handling oftraffic for different network slices that may be pre-configured and mayallow a single RAN node to support multiple slices. The new RAN maysupport selection of a RAN part for a given network slice, by one ormore slice ID(s) or NSSAI(s) provided by a UE or a NGC (e.g. NG CP). Theslice ID(s) or NSSAI(s) may identify one or more of pre-configurednetwork slices in a PLMN. For initial attach, a UE may provide a sliceID and/or an NSSAI, and a RAN node (e.g. gNB) may use the slice ID orthe NSSAI for routing an initial NAS signaling to an NGC control planefunction (e.g. NG CP). If a UE does not provide any slice ID or NSSAI, aRAN node may send a NAS signaling to a default NGC control planefunction. For subsequent accesses, the UE may provide a temporary ID fora slice identification, which may be assigned by the NGC control planefunction, to enable a RAN node to route the NAS message to a relevantNGC control plane function. The new RAN may support resource isolationbetween slices. The RAN resource isolation may be achieved by avoidingthat shortage of shared resources in one slice breaks a service levelagreement for another slice.

The amount of data traffic carried over cellular networks is expected toincrease for many years to come. The number of users/devices isincreasing, and each user/device accesses an increasing number andvariety of services, e.g. video delivery, large files, images. Thisrequires not only high capacity in the network, but also provisioningvery high data rates to meet customers' expectations on interactivityand responsiveness. More spectrum is therefore needed for cellularoperators to meet the increasing demand. Considering user expectationsof high data rates along with seamless mobility, it is beneficial thatmore spectrum be made available for deploying macro cells as well assmall cells for cellular systems.

Striving to meet the market demands, there has been increasing interestfrom operators in deploying some complementary access utilizingunlicensed spectrum to meet the traffic growth. This is exemplified bythe large number of operator-deployed Wi-Fi networks and the 3GPPstandardization of LTE/WLAN interworking solutions. This interestindicates that unlicensed spectrum, when present, may be an effectivecomplement to licensed spectrum for cellular operators to helpaddressing the traffic explosion in some scenarios, such as hotspotareas. LAA offers an alternative for operators to make use of unlicensedspectrum while managing one radio network, thus offering newpossibilities for optimizing the network's efficiency.

In an example embodiment, Listen-before-talk (clear channel assessment)may be implemented for transmission in an LAA cell. In alisten-before-talk (LBT) procedure, equipment may apply a clear channelassessment (CCA) check before using the channel. For example, the CCAutilizes at least energy detection to determine the presence or absenceof other signals on a channel in order to determine if a channel isoccupied or clear, respectively. For example, European and Japaneseregulations mandate the usage of LBT in the unlicensed bands. Apart fromregulatory requirements, carrier sensing via LBT may be one way for fairsharing of the unlicensed spectrum.

In an example embodiment, discontinuous transmission on an unlicensedcarrier with limited maximum transmission duration may be enabled. Someof these functions may be supported by one or more signals to betransmitted from the beginning of a discontinuous LAA downlinktransmission. Channel reservation may be enabled by the transmission ofsignals, by an LAA node, after gaining channel access via a successfulLBT operation, so that other nodes that receive the transmitted signalwith energy above a certain threshold sense the channel to be occupied.Functions that may need to be supported by one or more signals for LAAoperation with discontinuous downlink transmission may include one ormore of the following: detection of the LAA downlink transmission(including cell identification) by wireless devices; time & frequencysynchronization of wireless devices.

In an example embodiment, DL LAA design may employ subframe boundaryalignment according to LTE-A carrier aggregation timing relationshipsacross serving cells aggregated by CA. This may not imply that the basestation transmissions may start only at the subframe boundary. LAA maysupport transmitting PDSCH when not all OFDM symbols are available fortransmission in a subframe according to LBT. Delivery of necessarycontrol information for the PDSCH may also be supported.

LBT procedure may be employed for fair and friendly coexistence of LAAwith other operators and technologies operating in unlicensed spectrum.LBT procedures on a node attempting to transmit on a carrier inunlicensed spectrum require the node to perform a clear channelassessment to determine if the channel is free for use. An LBT proceduremay involve at least energy detection to determine if the channel isbeing used. For example, regulatory requirements in some regions, e.g.,in Europe, specify an energy detection threshold such that if a nodereceives energy greater than this threshold, the node assumes that thechannel is not free. While nodes may follow such regulatoryrequirements, a node may optionally use a lower threshold for energydetection than that specified by regulatory requirements. In an example,LAA may employ a mechanism to adaptively change the energy detectionthreshold, e.g., LAA may employ a mechanism to adaptively lower theenergy detection threshold from an upper bound. Adaptation mechanism maynot preclude static or semi-static setting of the threshold. In anexample Category 4 LBT mechanism or other type of LBT mechanisms may beimplemented.

Various example LBT mechanisms may be implemented. In an example, forsome signals, in some implementation scenarios, in some situations,and/or in some frequencies no LBT procedure may performed by thetransmitting entity. In an example, Category 2 (e.g. LBT without randomback-off) may be implemented. The duration of time that the channel issensed to be idle before the transmitting entity transmits may bedeterministic. In an example, Category 3 (e.g. LBT with random back-offwith a contention window of fixed size) may be implemented. The LBTprocedure may have the following procedure as one of its components. Thetransmitting entity may draw a random number N within a contentionwindow. The size of the contention window may be specified by theminimum and maximum value of N. The size of the contention window may befixed. The random number N may be employed in the LBT procedure todetermine the duration of time that the channel is sensed to be idlebefore the transmitting entity transmits on the channel. In an example,Category 4 (e.g. LBT with random back-off with a contention window ofvariable size) may be implemented. The transmitting entity may draw arandom number N within a contention window. The size of contentionwindow may be specified by the minimum and maximum value of N. Thetransmitting entity may vary the size of the contention window whendrawing the random number N. The random number N is used in the LBTprocedure to determine the duration of time that the channel is sensedto be idle before the transmitting entity transmits on the channel.

LAA may employ uplink LBT at the wireless device. The UL LBT scheme maybe different from the DL LBT scheme (e.g. by using different LBTmechanisms or parameters) for example, since the LAA UL is based onscheduled access which affects a wireless device's channel contentionopportunities. Other considerations motivating a different UL LBT schemeinclude, but are not limited to, multiplexing of multiple wirelessdevices in a single subframe.

In an example, a DL transmission burst may be a continuous transmissionfrom a DL transmitting node with no transmission immediately before orafter from the same node on the same CC. An UL transmission burst from awireless device perspective may be a continuous transmission from awireless device with no transmission immediately before or after fromthe same wireless device on the same CC. In an example, UL transmissionburst is defined from a wireless device perspective. In an example, anUL transmission burst may be defined from a base station perspective. Inan example, in case of a base station operating DL+UL LAA over the sameunlicensed carrier, DL transmission burst(s) and UL transmissionburst(s) on LAA may be scheduled in a TDM manner over the sameunlicensed carrier. For example, an instant in time may be part of a DLtransmission burst or an UL transmission burst.

A New Radio (NR) system may support both single beam and multi-beamoperations. In a multi-beam system, a base station (e.g., gNB) mayperform a downlink beam sweeping to provide coverage for downlinkSynchronization Signals (SSs) and common control channels. A UserEquipment (UE) may perform an uplink beam sweeping for uplink directionto access a cell. In a single beam scenario, a gNB may configuretime-repetition transmission for one SS block, which may comprise atleast Primary Synchronization Signal (PSS), Secondary SynchronizationSignal (SSS), and Physical Broadcast Channel (PBCH), with a wide beam.In a multi-beam scenario, a gNB may configure at least some of thesesignals and physical channels in multiple beams. A UE may identify atleast OFDM symbol index, slot index in a radio frame and radio framenumber from an SS block.

In an example, in an RRC_INACTIVE state or RRC_IDLE state, a UE mayassume that SS blocks form an SS burst, and an SS burst set. An SS burstset may have a given periodicity. In multi-beam scenarios, SS blocks maybe transmitted in multiple beams, together forming an SS burst. One ormore SS blocks may be transmitted on one beam. A beam has a steeringdirection. If multiple SS bursts are transmitted with beams, these SSbursts together may form an SS burst set as shown in FIG. 15. A basestation 1501 (e.g., a gNB in NR) may transmit SS bursts 1502A to 1502Hduring time periods 1503. A plurality of these SS bursts may comprise anSS burst set, such as an SS burst set 1504 (e.g., SS bursts 1502A and1502E). An SS burst set may comprise any number of a plurality of SSbursts 1502A to 1502H. Each SS burst within an SS burst set maytransmitted at a fixed or variable periodicity during time periods 1503.

An SS may be based on Cyclic Prefix-Orthogonal Frequency DivisionMultiplexing (CP-OFDM). The SS may comprise at least two types ofsynchronization signals; NR-PSS (Primary synchronization signal) andNR-SSS (Secondary synchronization signal). NR-PSS may be defined atleast for initial symbol boundary synchronization to the NR cell. NR-SSSmay be defined for detection of NR cell ID or at least part of NR cellID. NR-SSS detection may be based on the fixed time/frequencyrelationship with NR-PSS resource position irrespective of duplex modeand beam operation type at least within a given frequency range and CPoverhead. Normal CP may be supported for NR-PSS and NR-SSS.

The NR may comprise at least one physical broadcast channel (NR-PBCH).When a gNB transmit (or broadcast) the NR-PBCH, a UE may decode theNR-PBCH based on the fixed relationship with NR-PSS and/or NR-SSSresource position irrespective of duplex mode and beam operation type atleast within a given frequency range and CP overhead. NR-PBCH may be anon-scheduled broadcast channel carrying at least a part of minimumsystem information with fixed payload size and periodicity predefined inthe specification depending on carrier frequency range.

In single beam and multi-beam scenarios, NR may comprise an SS blockthat may support time (frequency, and/or spatial) division multiplexingof NR-PSS, NR-SSS, and NR-PBCH. A gNB may transmit NR-PSS, NR-SSS and/orNR-PBCH within an SS block. For a given frequency band, an SS block maycorrespond to N OFDM symbols based on the default subcarrier spacing,and N may be a constant. The signal multiplexing structure may be fixedin NR. A wireless device may identify, e.g., from an SS block, an OFDMsymbol index, a slot index in a radio frame, and a radio frame numberfrom an SS block.

A NR may support an SS burst comprising one or more SS blocks. An SSburst set may comprise one or more SS bursts. For example, a number ofSS bursts within a SS burst set may be finite. From physical layerspecification perspective, NR may support at least one periodicity of SSburst set. From UE perspective, SS burst set transmission may beperiodic, and UE may assume that a given SS block is repeated with an SSburst set periodicity.

Within an SS burst set periodicity, NR-PBCH repeated in one or more SSblocks may change. A set of possible SS block time locations may bespecified per frequency band in an RRC message. The maximum number ofSS-blocks within SS burst set may be carrier frequency dependent. Theposition(s) of actual transmitted SS-blocks may be informed at least forhelping CONNECTED/IDLE mode measurement, for helping CONNECTED mode UEto receive downlink (DL) data/control in one or more SS-blocks, or forhelping IDLE mode UE to receive DL data/control in one or moreSS-blocks. A UE may not assume that the gNB transmits the same number ofphysical beam(s). A UE may not assume the same physical beam(s) acrossdifferent SS-blocks within an SS burst set. For an initial cellselection, UE may assume default SS burst set periodicity which may bebroadcast via an RRC message and frequency band-dependent. At least formulti-beams operation case, the time index of SS-block may be indicatedto the UE.

For CONNECTED and IDLE mode UEs, NR may support network indication of SSburst set periodicity and information to derive measurementtiming/duration (e.g., time window for NR-SS detection). A gNB mayprovide (e.g., via broadcasting an RRC message) one SS burst setperiodicity information per frequency carrier to UE and information toderive measurement timing/duration if possible. In case that one SSburst set periodicity and one information regarding timing/duration areindicated, a UE may assume the periodicity and timing/duration for allcells on the same carrier. If a gNB does not provide indication of SSburst set periodicity and information to derive measurementtiming/duration, a UE may assume a predefined periodicity, e.g., 5 ms,as the SS burst set periodicity. NR may support set of SS burst setperiodicity values for adaptation and network indication.

For initial access, a UE may assume a signal corresponding to a specificsubcarrier spacing of NR-PSS/SSS in a given frequency band given by a NRspecification. For NR-PSS, a Zadoff-Chu (ZC) sequence may be employed asa sequence for NR-PSS. NR may define at least one basic sequence lengthfor a SS in case of sequence-based SS design. The number of antenna portof NR-PSS may be 1. For NR-PBCH transmission, NR may support a fixednumber of antenna port(s). A UE may not be required for a blinddetection of NR-PBCH transmission scheme or number of antenna ports. AUE may assume the same PBCH numerology as that of NR-SS. For the minimumsystem information delivery, NR-PBCH may comprise a part of minimumsystem information. NR-PBCH contents may comprise at least a part of theSFN (system frame number) or CRC. A gNB may transmit the remainingminimum system information in shared downlink channel via NR-PDSCH.

In a multi-beam example, one or more of PSS, SSS, or PBCH signals may berepeated for a cell, e.g., to support cell selection, cell reselection,and/or initial access procedures. For an SS burst, an associated PBCH ora physical downlink shared channel (PDSCH) scheduling system informationmay be broadcasted by a base station to multiple wireless devices. ThePDSCH may be indicated by a physical downlink control channel (PDCCH) ina common search space. The system information may comprise a physicalrandom access channel (PRACH) configuration for a beam. For a beam, abase station (e.g., a gNB in NR) may have a RACH configuration which mayinclude a PRACH preamble pool, time and/or frequency radio resources,and other power related parameters. A wireless device may use a PRACHpreamble from a RACH configuration to initiate a contention-based RACHprocedure or a contention-free RACH procedure. A wireless device mayperform a 4-step RACH procedure, which may be a contention-based RACHprocedure or a contention-free RACH procedure. The wireless device mayselect a beam associated with an SS block that may have the bestreceiving signal quality. The wireless device may successfully detect acell identifier associated with the cell and decode system informationwith a RACH configuration. The wireless device may use one PRACHpreamble and select one PRACH resource from RACH resources indicated bythe system information associated with the selected beam. A PRACHresource may comprise at least one of: a PRACH index indicating a PRACHpreamble, a PRACH format, a PRACH numerology, time and/or frequencyradio resource allocation, power setting of a PRACH transmission, and/orother radio resource parameters. For a contention-free RACH procedure,the PRACH preamble and resource may be indicated in a DCI or other highlayer signaling.

In an example, a UE may detect one or more PSS/SSS/PBCH for cellselection/reselection and/or initial access procedures. PBCH, or aPhysical Downlink Shared Channel (PDSCH), indicated by a PhysicalDownlink Control Channel (PDCCH) in common search space, scheduling asystem information, such as System Information Block type 2 (SIB2), maybe broadcasted to multiple UEs. In an example, SIB2 may carry one ormore Physical Random Access Channel (PRACH) configuration. In anexample, a gNB may have one or more Random Access Channel (RACH)configuration which may include PRACH preamble pool, time/frequencyradio resources, and other power related parameters. A UE may select aPRACH preamble from a RACH configuration to initiate a contention-basedRACH procedure, or a contention-free RACH procedure.

In an example, a UE may perform a 4-step RACH procedure, which may be acontention-based or contention-free RACH procedure. A four-step randomaccess (RA) procedure may comprise RA preamble (RAP) transmission in thefirst step, random access response (RAR) transmission in the secondstep, scheduled transmission of one or more transport blocks (TBs) inthe third step, and contention resolution in the fourth step as shown inFIG. 16. Specifically, FIG. 16A shows a contention-based 4-step RAprocedure, and FIG. 16B shows a contention-free RA procedure.

In the first step, a UE may transmit a RAP using a configured RApreamble format with a Tx beam. RA channel (RACH) resource may bedefined as a time-frequency resource to transmit a RAP. Broadcast systeminformation may inform whether a UE needs to transmit one ormultiple/repeated preamble within a subset of RACH resources.

A base station may configure an association between DL signal/channel,and a subset of RACH resources and/or a subset of RAP indices, fordetermining the downlink (DL) transmission in the second step. Based onthe DL measurement and the corresponding association, a UE may selectthe subset of RACH resources and/or the subset of RAP indices. In anexample, there may be two RAP groups informed by broadcast systeminformation and one may be optional. If a base station configures thetwo groups in the four-step RA procedure, a UE may determine which groupthe UE selects a RAP from, based on the pathloss and a size of themessage to be transmitted by the UE in the third step. A base stationmay use a group type to which a RAP belongs as an indication of themessage size in the third step and the radio conditions at a UE. A basestation may broadcast the RAP grouping information along with one ormore thresholds on system information.

In the second step of the four-step RA procedure, a base station maytransmit a RA response (RAR) to the UE in response to reception of a RAPthat the UE transmits. A UE may monitor the PDCCH carrying a DCI, todetect RAR transmitted on a PDSCH in a RA Response window. The DCI maybe CRC-scrambled by the RA-RNTI (Random Access-Radio Network TemporaryIdentifier). RA-RNTI may be used on the PDCCH when Random AccessResponse messages are transmitted. It may unambiguously identify whichtime-frequency resource is used by the MAC entity to transmit the RandomAccess preamble. The RA Response window may start at the subframe thatcontains the end of a RAP transmission plus three subframes. The RAResponse window may have a length indicated by ra-ResponseWindowSize. AUE may compute the RA-RNTI associated with the PRACH in which the UEtransmits a RAP as: RA-RNTI=1+t_id+10*f_id, where t_id is an index of afirst subframe of a specified PRACH (0≤t_id<10), and f_id is an index ofa specified PRACH within the subframe, in ascending order of frequencydomain (0≤f_id<6). In an example, different types of UEs, e.g. NB-IoT,BL-UE, or UE-EC may employ different formulas for RA-RNTI calculations.

A UE may stop monitoring for RAR(s) after decoding of a MAC packet dataunit (PDU) for RAR comprising a RAP identifier (RAPID) that matches theRAP transmitted by the UE. The MAC PDU may comprise one or more MAC RARsand a MAC header that may comprise a subheader having a backoffindicator (BI) and one or more subheader that comprises RAPIDs.

FIG. 17 illustrates an example of a MAC PDU comprising a MAC header andMAC RARs for a four-step RA procedure. If a RAR comprises a RAPIDcorresponding to a RAP that a UE transmits, the UE may process the data,such as a timing advance (TA) command, a UL grant, and a TemporaryC-RNTI (TC-RNTI), in the RAR.

FIG. 18A, FIG. 18B and FIG. 18C show contents of a MAC RAR.Specifically, FIG. 18A shows the contents of a MAC RAR of a normal UE.FIG. 18B shows the contents of a MAC RAR of a MTC UE. FIG. 18C shows thecontents of MAC RAR of a NB-IOT UE.

In the third step of the four-step RA procedure, a UE may adjust UL timealignment by using the TA value corresponding to the TA command in thereceived RAR in the second step and may transmit the one or more TBs toa base station using the UL resources assigned in the UL grant in thereceived RAR. The TBs that a UE transmits in the third step may compriseRRC signaling, such as RRC connection request, RRC connectionRe-establishment request, or RRC connection resume request, and a UEidentity. The identity transmitted in the third step is used as part ofthe contention-resolution mechanism in the fourth step.

The fourth step in the four-step RA procedure may comprise a DL messagefor contention resolution. In an example, one or more UEs may performsimultaneous RA attempts selecting the same RAP in the first step andreceive the same RAR with the same TC-RNTI in the second step. Thecontention resolution in the fourth step may be to ensure that a UE doesnot incorrectly use another UE Identity. The contention resolutionmechanism may be based on either C-RNTI on PDCCH or UE ContentionResolution Identity on DL-SCH, depending on whether a UE has a C-RNTI ornot. If a UE has C-RNTI, upon detection of C-RNTI on the PDCCH, the UEmay determine the success of RA procedure. If a UE does not have C-RNTIpre-assigned, the UE may monitor DL-SCH associated with TC-RNTI that abase station transmits in a RAR of the second step and compare theidentity in the data transmitted by the base station on DL-SCH in thefourth step with the identity that the UE transmits in the third step.If the two identities are identical, the UE may determine the success ofRA procedure and promote the TC-RNTI to the C-RNTI.

The forth step in the four-step RA procedure may allow HARQretransmission. A UE may start mac-ContentionResolutionTimer when the UEtransmits one or more TBs to a base station in the third step and mayrestart mac-ContentionResolutionTimer at each HARQ retransmission. Whena UE receives data on the DL resources identified by C-RNTI or TC-RNTIin the fourth step, the UE may stop the mac-ContentionResolutionTimer.If the UE does not detect the contention resolution identity thatmatches to the identity transmitted by the UE in the third step, the UEmay determine the failure of RA procedure and discard the TC-RNTI. Ifmac-ContentionResolutionTimer expires, the UE may determine the failureof RA procedure and discard the TC-RNTI. If the contention resolution isfailed, a UE may flush the HARQ buffer used for transmission of the MACPDU and may restart the four-step RA procedure from the first step. TheUE may delay the subsequent RAP transmission by the backoff timerandomly selected according to a uniform distribution between 0 and thebackoff parameter value corresponding the BI in the MAC PDU for RAR.

In a four-step RA procedure, the usage of the first two steps may be toobtain UL time alignment for a UE and obtain an uplink grant. The thirdand fourth steps may be used to setup RRC connections, and/or resolvecontention from different UEs.

FIG. 19 shows an example of a random access procedure (e.g., via a RACH)that may include sending, by a base station, one or more SS blocks. Awireless device 1920 (e.g., a UE) may transmit one or more preambles toa base station 1921 (e.g., a gNB in NR). Each preamble transmission bythe wireless device may be associated with a separate random accessprocedure, such as shown in FIG. 19. The random access procedure maybegin at step 1901 with a base station 1921 (e.g., a gNB in NR) sendinga first SS block to a wireless device 1921 (e.g., a UE). Any of the SSblocks may comprise one or more of a PSS, SSS, tertiary synchronizationsignal (TSS), or PBCH signal. The first SS block in step 1901 may beassociated with a first PRACH configuration. At step 1902, the basestation 1921 may send to the wireless device 1920 a second SS block thatmay be associated with a second PRACH configuration. At step 1903, thebase station 1921 may send to the wireless device 1920 a third SS blockthat may be associated with a third PRACH configuration. At step 1904,the base station 1921 may send to the wireless device 1920 a fourth SSblock that may be associated with a fourth PRACH configuration. Anynumber of SS blocks may be sent in the same manner in addition to, orreplacing, steps 1903 and 1904. An SS burst may comprise any number ofSS blocks. For example, SS burst 1910 comprises the three SS blocks sentduring steps 1902-1904.

The wireless device 1920 may send to the base station 1921 a preamble,at step 1905, e.g., after or in response to receiving one or more SSblocks or SS bursts. The preamble may comprise a PRACH preamble and maybe referred to as RA Msg 1. The PRACH preamble may be transmitted instep 1905 according to or based on a PRACH configuration that may bereceived in an SS block (e.g., one of the SS blocks from steps1901-1904) that may be determined to be the best SS block beam. Thewireless device 1920 may determine a best SS block beam from among SSblocks it may receive prior to sending the PRACH preamble. The basestation 1921 may send a random access response (RAR), which may bereferred to as RA Msg2, at step 1906, e.g., after or in response toreceiving the PRACH preamble. The RAR may be transmitted in step 1906via a DL beam that corresponds to the SS block beam associated with thePRACH configuration. The base station 1921 may determine the best SSblock beam from among SS blocks it previously sent prior to receivingthe PRACH preamble. The base station 1621 may receive the PRACH preambleaccording to or based on the PRACH configuration associated with thebest SS block beam.

The wireless device 1920 may send to the base station 1921 anRRCConnectionRequest and/or RRCConnectionResumeRequest message, whichmay be referred to as RA Msg3, at step 1907, e.g., after or in responseto receiving the RAR. The base station 1921 may send to the wirelessdevice 1920 an RRCConnectionSetup and/or RRCConnectionResume message,which may be referred to as RA Msg4, at step 1908, e.g., after or inresponse to receiving the RRCConnectionRequest and/orRRCConnectionResumeRequest message. The wireless device 1920 may send tothe base station 1921 an RRCConnectionSetupComplete and/orRRCConnectionResumeComplete message, which may be referred to as RAMsg5, at step 1909, e.g., after or in response to receiving theRRCConnectionSetup and/or RRCConnectionResume. An RRC connection may beestablished between the wireless device 1920 and the base station 1921,and the random access procedure may end, e.g., after or in response toreceiving the RRCConnectionSetupComplete and/orRRCConnectionResumeComplete message.

A best beam, including but not limited to a best SS block beam, may bedetermined based on a channel state information reference signal(CSI-RS). A wireless device may use a CSI-RS in a multi-beam system forestimating the beam quality of the links between the wireless device anda base station. For example, based on a measurement of a CSI-RS, awireless device may report CSI for downlink channel adaption. A CSIparameter may include a precoding matrix index (PMI), a channel qualityindex (CQI) value, and/or a rank indicator (RI). A wireless device mayreport a beam index based on a reference signal received power (RSRP)measurement on a CSI-RS. The wireless device may report the beam indexin a CSI resource indication (CRI) for downlink beam selection. A basestation may transmit a CSI-RS via a CSI-RS resource, such as via one ormore antenna ports, or via one or more time and/or frequency radioresources. A beam may be associated with a CSI-RS. A CSI-RS may comprisean indication of a beam direction. Each of a plurality of beams may beassociated with one of a plurality of CSI-RSs. A CSI-RS resource may beconfigured in a cell-specific way, e.g., via common RRC signaling.Additionally or alternatively, a CSI-RS resource may be configured in awireless device-specific way, e.g., via dedicated RRC signaling and/orlayer 1 and/or layer 2 (L1/L2) signaling. Multiple wireless devices inor served by a cell may measure a cell-specific CSI-RS resource. Adedicated subset of wireless devices in or served by a cell may measurea wireless device-specific CSI-RS resource. A base station may transmita CSI-RS resource periodically, using aperiodic transmission, or using amulti-shot or semi-persistent transmission. In a periodic transmission,a base station may transmit the configured CSI-RS resource using aconfigured periodicity in the time domain. In an aperiodic transmission,a base station may transmit the configured CSI-RS resource in adedicated time slot. In a multi-shot or semi-persistent transmission, abase station may transmit the configured CSI-RS resource in a configuredperiod. A base station may configure different CSI-RS resources indifferent terms for different purposes. Different terms may include,e.g., cell-specific, device-specific, periodic, aperiodic, multi-shot,or other terms. Different purposes may include, e.g., beam management,CQI reporting, or other purposes.

FIG. 20 shows an example of transmitting CSI-RSs periodically for abeam. A base station 2001 may transmit a beam in a predefined order inthe time domain, such as during time periods 2003. Beams used for aCSI-RS transmission, such as for CSI-RS 2004 in transmissions 2002Cand/or 2003E, may have a different beam width relative to a beam widthfor SS-blocks transmission, such as for SS blocks 2002A, 2002B, 2002D,and 2002F-2002H. Additionally or alternatively, a beam width of a beamused for a CSI-RS transmission may have the same value as a beam widthfor an SS block. Some or all of one or more CSI-RSs may be included inone or more beams. An SS block may occupy a number of OFDM symbols(e.g., 4), and a number of subcarriers (e.g., 240), carrying asynchronization sequence signal. The synchronization sequence signal mayidentify a cell.

FIG. 21 shows an example of a CSI-RS that may be mapped in time andfrequency domains. Each square shown in FIG. 21 may represent a resourceblock within a bandwidth of a cell. Each resource block may comprise anumber of subcarriers. A cell may have a bandwidth comprising a numberof resource blocks. A base station (e.g., a gNB in NR) may transmit oneor more Radio Resource Control (RRC) messages comprising CSI-RS resourceconfiguration parameters for one or more CSI-RS. One or more of thefollowing parameters may be configured by higher layer signaling foreach CSI-RS resource configuration: CSI-RS resource configurationidentity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol andRE locations in a subframe), CSI-RS subframe configuration (e.g.,subframe location, offset, and periodicity in a radio frame), CSI-RSpower parameter, CSI-RS sequence parameter, CDM type parameter,frequency density, transmission comb, QCL parameters (e.g.,QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist,csi-rs-configZPid, qcl-csi-rs-configNZPid), and/or other radio resourceparameters.

FIG. 21 shows three beams that may be configured for a wireless device,e.g., in a wireless device-specific configuration. Any number ofadditional beams (e.g., represented by the column of blank squares) orfewer beams may be included. Beam 1 may be allocated with CSI-RS 1 thatmay be transmitted in some subcarriers in a resource block (RB) of afirst symbol. Beam 2 may be allocated with CSI-RS 2 that may betransmitted in some subcarriers in an RB of a second symbol. Beam 3 maybe allocated with CSI-RS 3 that may be transmitted in some subcarriersin an RB of a third symbol. All subcarriers in an RB may not necessarilybe used for transmitting a particular CSI-RS (e.g., CSI-RS 1) on anassociated beam (e.g., beam 1) for that CSI-RS. By using frequencydivision multiplexing (FDM), other subcarriers, not used for beam 1 forthe wireless device in the same RB, may be used for other CSI-RStransmissions associated with a different beam for other wirelessdevices. Additionally or alternatively, by using time domainmultiplexing (TDM), beams used for a wireless device may be configuredsuch that different beams (e.g., beam 1, beam 2, and beam 3) for thewireless device may be transmitted using some symbols different frombeams of other wireless devices.

Beam management may use a device-specific configured CSI-RS. In a beammanagement procedure, a wireless device may monitor a channel quality ofa beam pair link comprising a transmitting beam by a base station (e.g.,a gNB in NR) and a receiving beam by the wireless device (e.g., a UE).When multiple CSI-RSs associated with multiple beams are configured, awireless device may monitor multiple beam pair links between the basestation and the wireless device.

A wireless device may transmit one or more beam management reports to abase station. A beam management report may indicate one or more beampair quality parameters, comprising, e.g., one or more beamidentifications, RSRP, PMI, CQI, and/or RI, of a subset of configuredbeams.

A base station and/or a wireless device may perform a downlink L1/L2beam management procedure. One or more downlink L1/L2 beam managementprocedures may be performed within one or multiple transmission andreceiving points (TRPs), such as shown in FIG. 23A and FIG. 23B,respectively.

FIG. 22 shows examples of three beam management procedures, P1, P2, andP3. Procedure P1 may be used to enable a wireless device measurement ondifferent transmit (Tx) beams of a TRP (or multiple TRPs), e.g., tosupport a selection of Tx beams and/or wireless device receive (Rx)beam(s) (shown as ovals in the top row and bottom row, respectively, ofP1). Beamforming at a TRP (or multiple TRPs) may include, e.g., anintra-TRP and/or inter-TRP Tx beam sweep from a set of different beams(shown, in the top rows of P1 and P2, as ovals rotated in acounter-clockwise direction indicated by the dashed arrow). Beamformingat a wireless device 2201, may include, e.g., a wireless device Rx beamsweep from a set of different beams (shown, in the bottom rows of P1 andP3, as ovals rotated in a clockwise direction indicated by the dashedarrow). Procedure P2 may be used to enable a wireless device measurementon different Tx beams of a TRP (or multiple TRPs) (shown, in the top rowof P2, as ovals rotated in a counter-clockwise direction indicated bythe dashed arrow), e.g., which may change inter-TRP and/or intra-TRP Txbeam(s). Procedure P2 may be performed, e.g., on a smaller set of beamsfor beam refinement than in procedure P1. P2 may be a particular exampleof P1. Procedure P3 may be used to enable a wireless device measurementon the same Tx beam (shown as oval in P3), e.g., to change a wirelessdevice Rx beam if the wireless device 2201 uses beamforming.

A wireless device 2201 (e.g., a UE) and/or abase station 2202 (e.g., agNB) may trigger a beam failure recovery mechanism. The wireless device2201 may trigger a beam failure recovery (BFR) request transmission,e.g., if a beam failure event occurs. A beam failure event may include,e.g., a determination that a quality of beam pair link(s) of anassociated control channel is unsatisfactory. A determination of anunsatisfactory quality of beam pair link(s) of an associated channel maybe based on the quality falling below a threshold and/or an expirationof a timer.

The wireless device 2201 may measure a quality of beam pair link(s)using one or more reference signals (RS). One or more SS blocks, one ormore CSI-RS resources, and/or one or more demodulation reference signals(DM-RSs) of a PBCH may be used as a RS for measuring a quality of a beampair link. Each of the one or more CSI-RS resources may be associatedwith a CSI-RS resource index (CRI). A quality of a beam pair link may bebased on one or more of an RSRP value, reference signal received quality(RSRQ) value, and/or CSI value measured on RS resources. The basestation 2202 may indicate that an RS resource, e.g., that may be usedfor measuring a beam pair link quality, is quasi-co-located (QCLed) withone or more DM-RSs of a control channel. The RS resource and the DM-RSsof the control channel may be QCLed when the channel characteristicsfrom a transmission via an RS to the wireless device 2201, and thechannel characteristics from a transmission via a control channel to thewireless device, are similar or the same under a configured criterion.

FIG. 23A shows an example of a beam failure event involving a singleTRP. A single TRP such as at a base station 2301 may transmit, to awireless device 2302, a first beam 2303 and a second beam 2304. A beamfailure event may occur if, e.g., a serving beam, such as the secondbeam 2304, is blocked by a moving vehicle 2305 or other obstruction(e.g., building, tree, land, or any object) and configured beams (e.g.,the first beam 2303 and/or the second beam 2304), including the servingbeam, are received from the single TRP. The wireless device 2302 maytrigger a mechanism to recover from beam failure when a beam failureoccurs.

FIG. 23B shows an example of a beam failure event involving multipleTRPs. Multiple TRPs, such as at a first base station 2306 and at asecond base station 2309, may transmit, to a wireless device 2308, afirst beam 2307 (e.g., from the first base station 2306) and a secondbeam 2310 (e.g., from the second base station 2309). A beam failureevent may occur when, e.g., a serving beam, such as the second beam2310, is blocked by a moving vehicle 2311 or other obstruction (e.g.,building, tree, land, or any object) and configured beams (e.g., thefirst beam 2307 and/or the second beam 2310) are received from multipleTRPs. The wireless device 2008 may trigger a mechanism to recover frombeam failure when a beam failure occurs.

A wireless device may monitor a PDCCH, such as a New Radio PDCCH(NR-PDCCH), on M beam pair links simultaneously, where M≥1 and themaximum value of M may depend at least on the wireless devicecapability. Such monitoring may increase robustness against beam pairlink blocking. A base station may transmit, and the wireless device mayreceive, one or more messages configured to cause the wireless device tomonitor NR-PDCCH on different beam pair link(s) and/or in differentNR-PDCCH OFDM symbol.

A base station may transmit higher layer signaling, and/or a MAC controlelement (MAC CE), that may comprise parameters related to a wirelessdevice Rx beam setting for monitoring NR-PDCCH on multiple beam pairlinks. A base station may transmit one or more indications of a spatialQCL assumption between a first DL RS antenna port(s) and a second DL RSantenna port(s). The first DL RS antenna port(s) may be for one or moreof a cell-specific CSI-RS, device-specific CSI-RS, SS block, PBCH withDM-RSs of PBCH, and/or PBCH without DM-RSs of PBCH. The second DL RSantenna port(s) may be for demodulation of a DL control channel.Signaling for a beam indication for a NR-PDCCH (e.g., configuration tomonitor NR-PDCCH) may be via MAC CE signaling, RRC signaling, DCIsignaling, or specification-transparent and/or an implicit method, andany combination thereof.

For reception of unicast DL data channel, a base station may indicatespatial QCL parameters between DL RS antenna port(s) and DM-RS antennaport(s) of DL data channel. A base station may transmit DCI (e.g.,downlink grants) comprising information indicating the RS antennaport(s). The information may indicate the RS antenna port(s) which maybe QCLed with DM-RS antenna port(s). A different set of DM-RS antennaport(s) for the DL data channel may be indicated as a QCL with adifferent set of RS antenna port(s).

If a base station transmits a signal indicating a spatial QCL parametersbetween CSI-RS and DM-RS for PDCCH, a wireless device may use CSI-RSsQCLed with DM-RS for a PDCCH to monitor beam pair link quality. If abeam failure event occurs, the wireless device may transmit a beamfailure recovery request, such as by a determined configuration.

If a wireless device transmits a beam failure recovery request, e.g.,via an uplink physical channel or signal, a base station may detect thatthere is a beam failure event, for the wireless device, by monitoringthe uplink physical channel or signal. The base station may initiate abeam recovery mechanism to recover the beam pair link for transmittingPDCCH between the base station and the wireless device. The base stationmay transmit one or more control signals, to the wireless device, e.g.,after or in response to receiving the beam failure recovery request. Abeam recovery mechanism may be, e.g., an L1 scheme, or a higher layerscheme.

A base station may transmit one or more messages comprising, e.g.,configuration parameters of an uplink physical channel and/or a signalfor transmitting a beam failure recovery request. The uplink physicalchannel and/or signal may be based on at least one of the following: anon-contention based PRACH (e.g., a beam failure recovery PRACH orBFR-PRACH), which may use a resource orthogonal to resources of otherPRACH transmissions; a PUCCH (e.g., beam failure recovery PUCCH orBFR-PUCCH); and/or a contention-based PRACH resource. Combinations ofthese candidate signal and/or channels may be configured by a basestation.

A gNB may respond a confirmation message to a UE after receiving one ormultiple BFR request. The confirmation message may include the CRIassociated with the candidate beam the UE indicates in the one ormultiple BFR request. The confirmation message may be a L1 controlinformation.

In carrier aggregation (CA), two or more component carriers (CCs) may beaggregated. A wireless device may simultaneously receive or transmit onone or more CCs, depending on capabilities of the wireless device, usingthe technique of CA. In an example, a wireless device may support CA forcontiguous CCs and/or for non-contiguous CCs. CCs may be organized intocells. For example, CCs may be organized into one primary cell (PCell)and one or more secondary cells (SCells).

When configured with CA, a wireless device may have one RRC connectionwith a network. During an RRC connectionestablishment/re-establishment/handover, a cell providing NAS mobilityinformation may be a serving cell. During an RRC connectionre-establishment/handover procedure, a cell providing a security inputmay be a serving cell. In an example, the serving cell may denote aPCell. In an example, a gNB may transmit, to a wireless device, one ormore messages comprising configuration parameters of a plurality of oneor more SCells, depending on capabilities of the wireless device.

When configured with CA, a base station and/or a wireless device mayemploy an activation/deactivation mechanism of an SCell to improvebattery or power consumption of the wireless device. When a wirelessdevice is configured with one or more SCells, a gNB may activate ordeactivate at least one of the one or more SCells. Upon configuration ofan SCell, the SCell may be deactivated unless an SCell state associatedwith the SCell is set to “activated” or “dormant”.

In an example, a wireless device may activate/deactivate an SCell inresponse to receiving an SCell Activation/Deactivation MAC CE.

In an example, a gNB may transmit, to a wireless device, one or moremessages comprising an SCell timer (e.g., sCellDeactivationTimer). In anexample, a wireless device may deactivate an SCell in response to anexpiry of the SCell timer.

When a wireless device receives an SCell Activation/Deactivation MAC CEactivating an SCell, the wireless device may activate the SCell. Inresponse to the activating the SCell, the wireless device may performoperations comprising: SRS transmissions on the SCell; CQI/PMI/RI/CRIreporting for the SCell; PDCCH monitoring on the SCell; PDCCH monitoringfor the SCell; and/or PUCCH transmissions on the SCell.

In an example, in response to the activating the SCell, the wirelessdevice may start or restart a first SCell timer (e.g.,sCellDeactivationTimer) associated with the SCell. The wireless devicemay start or restart the first SCell timer in the slot when the SCellActivation/Deactivation MAC CE activating the SCell has been received.In an example, in response to the activating the SCell, the wirelessdevice may (re-)initialize one or more suspended configured uplinkgrants of a configured grant Type 1 associated with the SCell accordingto a stored configuration. In an example, in response to the activatingthe SCell, the wireless device may trigger PHR.

When a wireless device receives an SCell Activation/Deactivation MAC CEdeactivating an activated SCell, the wireless device may deactivate theactivated SCell. In an example, when a first SCell timer (e.g.,sCellDeactivationTimer) associated with an activated SCell expires, thewireless device may deactivate the activated SCell. In response to thedeactivating the activated SCell, the wireless device may stop the firstSCell timer associated with the activated SCell. In an example, inresponse to the deactivating the activated SCell, the wireless devicemay clear one or more configured downlink assignments and/or one or moreconfigured uplink grants of a configured uplink grant Type 2 associatedwith the activated SCell. In an example, in response to the deactivatingthe activated SCell, the wireless device may: suspend one or moreconfigured uplink grants of a configured uplink grant Type 1 associatedwith the activated SCell; and/or flush HARQ buffers associated with theactivated SCell.

In an example, when an SCell is deactivated, a wireless device may notperform operations comprising: transmitting SRS on the SCell; reportingCQI/PMI/RI/CRI for the SCell; transmitting on UL-SCH on the SCell;transmitting on RACH on the SCell; monitoring at least one first PDCCHon the SCell; monitoring at least one second PDCCH for the SCell; and/ortransmitting a PUCCH on the SCell.

In an example, when at least one first PDCCH on an activated SCellindicates an uplink grant or a downlink assignment, a wireless devicemay restart a first SCell timer (e.g., sCellDeactivationTimer)associated with the activated SCell. In an example, when at least onesecond PDCCH on a serving cell (e.g. a PCell or an SCell configured withPUCCH, i.e. PUCCH SCell) scheduling the activated SCell indicates anuplink grant or a downlink assignment for the activated SCell, awireless device may restart the first SCell timer (e.g.,sCellDeactivationTimer) associated with the activated SCell.

In an example, when an SCell is deactivated, if there is an ongoingrandom access procedure on the SCell, a wireless device may abort theongoing random access procedure on the SCell.

FIG. 24A shows an example of an SCell Activation/Deactivation MAC CE ofone octet. A first MAC PDU subheader with a first LCID (e.g., ‘111010’)may identify the SCell Activation/Deactivation MAC CE of one octet. TheSCell Activation/Deactivation MAC CE of one octet may have a fixed size.The SCell Activation/Deactivation MAC CE of one octet may comprise asingle octet. The single octet may comprise a first number of C-fields(e.g. seven) and a second number of R-fields (e.g., one).

FIG. 24B shows an example of an SCell Activation/Deactivation MAC CE offour octets. A second MAC PDU subheader with a second LCID (e.g.,‘111001’) may identify the SCell Activation/Deactivation MAC CE of fouroctets. The SCell Activation/Deactivation MAC CE of four octets may havea fixed size. The SCell Activation/Deactivation MAC CE of four octetsmay comprise four octets. The four octets may comprise a third number ofC-fields (e.g., 31) and a fourth number of R-fields (e.g., 1).

In FIG. 24A and/or FIG. 24B, a C_(i) field may indicate anactivation/deactivation status of an SCell with an SCell index i if anSCell with SCell index i is configured. In an example, when the C_(i)field is set to one, an SCell with an SCell index i may be activated. Inan example, when the C_(i) field is set to zero, an SCell with an SCellindex i may be deactivated. In an example, if there is no SCellconfigured with SCell index i, the wireless device may ignore the C_(i)field. In FIG. 24A and FIG. 24B, an R field may indicate a reserved bit.The R field may be set to zero.

FIG. 25A and FIG. 25B show timeline when a UE receives a MAC activationcommand. When a UE receives a MAC activation command for a secondarycell in subframe n, the corresponding actions in the MAC layer shall beapplied no later than the minimum requirement defined in 3GPP TS 36.133or TS 38.133 and no earlier than subframe n+8, except for the following:the actions related to CSI reporting and the actions related to thesCellDeactivationTimer associated with the secondary cell, which shallbe applied in subframe n+8. When a UE receives a MAC deactivationcommand for a secondary cell or the sCellDeactivationTimer associatedwith the secondary cell expires in subframe n, the corresponding actionsin the MAC layer shall apply no later than the minimum requirementdefined in 3GPP TS 36.133 or TS 38.133, except for the actions relatedto CSI reporting which shall be applied in subframe n+8.

When a UE receives a MAC activation command for a secondary cell insubframe n, the actions related to CSI reporting and the actions relatedto the sCellDeactivationTimer associated with the secondary cell, areapplied in subframe n+8. When a UE receives a MAC deactivation commandfor a secondary cell or other deactivation conditions are met (e.g. thesCellDeactivationTimer associated with the secondary cell expires) insubframe n, the actions related to CSI reporting are applied in subframen+8. The UE starts reporting invalid or valid CSI for the SCell at the(n+8)^(th) subframe, and start or restart the sCellDeactivationTimerwhen receiving the MAC CE activating the SCell in the n^(th) subframe.For some UE having slow activation, it may report an invalid CSI(out-of-range CSI) at the (n+8)^(th) subframe, for some UE having aquick activation, it may report a valid CSI at the (n+8)^(th) subframe.

When a UE receives a MAC activation command for an SCell in subframe n,the UE starts reporting CQI/PMI/RI/PTI for the SCell at subframe n+8 andstarts or restarts the sCellDeactivationTimer associated with the SCellat subframe n+8. It is important to define the timing of these actionsfor both UE and eNB. For example, sCellDeactivationTimer is maintainedin both eNB and UE and it is important that both UE and eNB stop, startand/or restart this timer in the same TTI. Otherwise, thesCellDeactivationTimer in the UE may not be in-sync with thecorresponding sCellDeactivationTimer in the eNB. Also, eNB startsmonitoring and receiving CSI (CQI/PMI/RI/PTI) according to thepredefined timing in the same TTI and/or after UE starts transmittingthe CSI. If the CSI timings in UE and eNB are not coordinated based on acommon standard or air interface signaling the network operation mayresult in inefficient operations and/or errors.

FIG. 26 shows DCI formats for an example of 20 MHz FDD operation with 2Tx antennas at the base station and no carrier aggregation in an LTEsystem. In a NR system, the DCI formats may comprise at least one of:DCI format 0_0/0_1 indicating scheduling of PUSCH in a cell; DCI format1_0/1_1 indicating scheduling of PDSCH in a cell; DCI format 2_0notifying a group of UEs of slot format; DCI format 2_1 notifying agroup of UEs of PRB(s) and OFDM symbol(s) where a UE may assume notransmission is intended for the UE; DCI format 2_2 indicatingtransmission of TPC commands for PUCCH and PUSCH; and/or DCI format 2_3indicating transmission of a group of TPC commands for SRS transmissionby one or more UEs. In an example, a gNB may transmit a DCI via a PDCCHfor scheduling decision and power-control commends. More specifically,the DCI may comprise at least one of: downlink scheduling assignments,uplink scheduling grants, power-control commands. The downlinkscheduling assignments may comprise at least one of: PDSCH resourceindication, transport format, HARQ information, and control informationrelated to multiple antenna schemes, a command for power control of thePUCCH used for transmission of ACK/NACK in response to downlinkscheduling assignments. The uplink scheduling grants may comprise atleast one of: PUSCH resource indication, transport format, and HARQrelated information, a power control command of the PUSCH.

In an example, different types of control information may correspond todifferent DCI message sizes. For example, supporting spatialmultiplexing with noncontiguous allocation of RBs in the frequencydomain may require a larger scheduling message in comparison with anuplink grant allowing for frequency-contiguous allocation only. DCIs maybe categorized into different DCI formats, where a format corresponds toa certain message size and usage.

In an example, a UE may monitor one or more PDCCH to detect one or moreDCI with one or more DCI format. The one or more PDCCH may betransmitted in common search space or UE-specific search space. A UE maymonitor PDCCH with only a limited set of DCI format, to save powerconsumption. For example, a normal UE may not be required to detect aDCI with DCI format 6 which is used for an eMTC UE. The more DCI formatto be detected, the more power be consumed at the UE.

In an example, a UE may monitor one or more PDCCH candidates to detectone or more DCI with one or more DCI format. The one or more PDCCH maybe transmitted in common search space or UE-specific search space. A UEmay monitor PDCCH with only a limited set of DCI format, to save powerconsumption. For example, a normal UE may not be required to detect aDCI with DCI format 6 which is used for an eMTC UE. The more DCI formatto be detected, the more power be consumed at the UE.

In an example, the one or more PDCCH candidates that a UE monitors maybe defined in terms of PDCCH UE-specific search spaces. A PDCCHUE-specific search space at CCE aggregation level L∈{1, 2, 4, 8} may bedefined by a set of PDCCH candidates for CCE aggregation level L. In anexample, for a DCI format, a UE may be configured per serving cell byone or more higher layer parameters a number of PDCCH candidates per CCEaggregation level L.

In an example, in non-DRX mode operation, a UE may monitor one or morePDCCH candidate in control resource set q according to a periodicity ofW_(PDCCH, q) symbols that may be configured by one or more higher layerparameters for control resource set q.

In an example, if a UE is configured with higher layer parameter, e.g.,cif-InSchedulingCell, the carrier indicator field value may correspondto cif-InSchedulingCell.

In an example, for the serving cell on which a UE may monitor one ormore PDCCH candidate in a UE-specific search space, if the UE is notconfigured with a carrier indicator field, the UE may monitor the one ormore PDCCH candidates without carrier indicator field. In an example,for the serving cell on which a UE may monitor one or more PDCCHcandidates in a UE-specific search space, if a UE is configured with acarrier indicator field, the UE may monitor the one or more PDCCHcandidates with carrier indicator field.

In an example, a UE may not monitor one or more PDCCH candidates on asecondary cell if the UE is configured to monitor one or more PDCCHcandidates with carrier indicator field corresponding to that secondarycell in another serving cell. For example, for the serving cell on whichthe UE may monitor one or more PDCCH candidates, the UE may monitor theone or more PDCCH candidates at least for the same serving cell.

In an example, the information in the DCI formats used for downlinkscheduling can be organized into different groups, with the fieldpresent varying between the DCI formats, including at least one of:resource information, consisting of: carrier indicator (0 or 3 bits), RBallocation; HARQ process number; MCS, NDI, and RV (for the first TB);MCS, NDI and RV (for the second TB); MIMO related information; PDSCHresource-element mapping and QCI; Downlink assignment index (DAI); TPCfor PUCCH; SRS request (1 bit), triggering one-shot SRS transmission;ACK/NACK offset; DCI format 0/1A indication, used to differentiatebetween DCI format 1A and 0; and padding if necessary. The MIMO relatedinformation may comprise at least one of: PMI, precoding information,transport block swap flag, power offset between PDSCH and referencesignal, reference-signal scrambling sequence, number of layers, and/orantenna ports for the transmission.

In an example, the information in the DCI formats used for uplinkscheduling can be organized into different groups, with the fieldpresent varying between the DCI formats, including at least one of:resource information, consisting of: carrier indicator, resourceallocation type, RB allocation; MCS, NDI (for the first TB); MCS, NDI(for the second TB); phase rotation of the uplink DMRS; precodinginformation; CSI request, requesting an aperiodic CSI report; SRSrequest (2 bit), used to trigger aperiodic SRS transmission using one ofup to three preconfigured settings; uplink index/DAI; TPC for PUSCH; DCIformat 0/1A indication; and padding if necessary.

In an example, a gNB may perform CRC scrambling for a DCI, beforetransmitting the DCI via a PDCCH. The gNB may perform CRC scrambling bybit-wise addition (or Modulo-2 addition or exclusive OR (XOR) operation)of multiple bits of at least one wireless device identifier (e.g.,C-RNTI, CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, SP CSIC-RNTI, SRS-TPC-RNTI, INT-RNTI, SFI-RNTI, P-RNTI, SI-RNTI, RA-RNTI,and/or MCS-C-RNTI) with the CRC bits of the DCI. The wireless device maycheck the CRC bits of the DCI, when detecting the DCI. The wirelessdevice may receive the DCI when the CRC is scrambled by a sequence ofbits that is the same as the at least one wireless device identifier.

In a NR system, in order to support wide bandwidth operation, a gNB maytransmit one or more PDCCH in different control resource sets. A gNB maytransmit one or more RRC message comprising configuration parameters ofone or more control resource sets. At least one of the one or morecontrol resource sets may comprise at least one of: a first OFDM symbol;a number of consecutive OFDM symbols; a set of resource blocks; aCCE-to-REG mapping; and a REG bundle size, in case of interleavedCCE-to-REG mapping.

In an example, a wireless device may transmit one or more uplink controlinformation (UCI) via one or more PUCCH resources to a base station. Theone or more UCI may comprise at least one of: HARQ-ACK information;scheduling request (SR); and/or CSI report. In an example, a PUCCHresource may be identified by at least: frequency location (e.g.,starting PRB); and/or a PUCCH format associated with initial cyclicshift of a base sequence and time domain location (e.g., starting symbolindex). In an example, a PUCCH format may be PUCCH format 0, PUCCHformat 1, PUCCH format 2, PUCCH format 3, or PUCCH format 4. A PUCCHformat 0 may have a length of 1 or 2 OFDM symbols and be less than orequal to 2 bits. A PUCCH format 1 may occupy a number between 4 and 14of OFDM symbols and be less than or equal to 2 bits. A PUCCH format 2may occupy 1 or 2 OFDM symbols and be greater than 2 bits. A PUCCHformat 3 may occupy a number between 4 and 14 of OFDM symbols and begreater than 2 bits. A PUCCH format 4 may occupy a number between 4 and14 of OFDM symbols and be greater than 2 bits. The PUCCH resource may beconfigured on a PCell, or a PUCCH secondary cell.

In an example, when configured with multiple uplink BWPs, a base stationmay transmit to a wireless device, one or more RRC messages comprisingconfiguration parameters of one or more PUCCH resource sets (e.g., atmost 4 sets) on an uplink BWP of the multiple uplink BWPs. Each PUCCHresource set may be configured with a PUCCH resource set index, a listof PUCCH resources with each PUCCH resource being identified by a PUCCHresource identifier (e.g., pucch-Resourceid), and/or a maximum number ofUCI information bits a wireless device may transmit using one of theplurality of PUCCH resources in the PUCCH resource set.

In an example, when configured with one or more PUCCH resource sets, awireless device may select one of the one or more PUCCH resource setsbased on a total bit length of UCI information bits (e.g., HARQ-ARQbits, SR, and/or CSI) the wireless device will transmit. In an example,when the total bit length of UCI information bits is less than or equalto 2, the wireless device may select a first PUCCH resource set with thePUCCH resource set index equal to “0”. In an example, when the total bitlength of UCI information bits is greater than 2 and less than or equalto a first configured value, the wireless device may select a secondPUCCH resource set with the PUCCH resource set index equal to “1”. In anexample, when the total bit length of UCI information bits is greaterthan the first configured value and less than or equal to a secondconfigured value, the wireless device may select a third PUCCH resourceset with the PUCCH resource set index equal to “2”. In an example, whenthe total bit length of UCI information bits is greater than the secondconfigured value and less than or equal to a third value (e.g., 1706),the wireless device may select a fourth PUCCH resource set with thePUCCH resource set index equal to “3”.

In an example, a wireless device may determine, based on a number ofuplink symbols of UCI transmission and a number of UCI bits, a PUCCHformat from a plurality of PUCCH formats comprising PUCCH format 0,PUCCH format 1, PUCCH format 2, PUCCH format 3 and/or PUCCH format 4. Inan example, the wireless device may transmit UCI in a PUCCH using PUCCHformat 0 if the transmission is over 1 symbol or 2 symbols and thenumber of HARQ-ACK information bits with positive or negative SR(HARQ-ACK/SR bits) is 1 or 2. In an example, the wireless device maytransmit UCI in a PUCCH using PUCCH format 1 if the transmission is over4 or more symbols and the number of HARQ-ACK/SR bits is 1 or 2. In anexample, the wireless device may transmit UCI in a PUCCH using PUCCHformat 2 if the transmission is over 1 symbol or 2 symbols and thenumber of UCI bits is more than 2. In an example, the wireless devicemay transmit UCI in a PUCCH using PUCCH format 3 if the transmission isover 4 or more symbols, the number of UCI bits is more than 2 and PUCCHresource does not include an orthogonal cover code. In an example, thewireless device may transmit UCI in a PUCCH using PUCCH format 4 if thetransmission is over 4 or more symbols, the number of UCI bits is morethan 2 and the PUCCH resource includes an orthogonal cover code.

In an example, in order to transmit HARQ-ACK information on a PUCCHresource, a wireless device may determine the PUCCH resource from aPUCCH resource set. The PUCCH resource set may be determined asmentioned above. The wireless device may determine the PUCCH resourcebased on a PUCCH resource indicator field in a DCI (e.g., with a DCIformat 1_0 or DCI for 1_1) received on a PDCCH. A 3-bit PUCCH resourceindicator field in the DCI may indicate one of eight PUCCH resources inthe PUCCH resource set. The wireless device may transmit the HARQ-ACKinformation in a PUCCH resource indicated by the 3-bit PUCCH resourceindicator field in the DCI.

In an example, the wireless device may transmit one or more UCI bits viaa PUCCH resource of an active uplink BWP of a PCell or a PUCCH secondarycell. Since at most one active uplink BWP in a cell is supported for awireless device, the PUCCH resource indicated in the DCI is naturally aPUCCH resource on the active uplink BWP of the cell.

FIG. 27 shows example of multiple BWPs configuration. A gNB may transmitone or more messages comprising configuration parameters of one or morebandwidth parts (BWP) of a cell. The cell may be a PCell or a SCell. Theone or more messages may comprise: RRC connection reconfigurationmessage (e.g., RRCReconfiguration); RRC connection reestablishmentmessage (e.g., RRCRestablishment); and/or RRC connection setup message(e.g., RRCSetup). The one or more BWPs may have different numerologies.A gNB may transmit one or more control information for cross-BWPscheduling to a UE. One BWP may overlap with another BWP in frequencydomain.

In an example, a gNB may transmit one or more messages comprisingconfiguration parameters of one or more DL and/or UL BWPs for a cell,with at least one BWP as the active DL or UL BWP, and zero or one BWP asthe default DL or UL BWP. For the PCell, the active DL BWP may be the DLBWP on which the UE may monitor one or more PDCCH, and/or receive PDSCH.The active UL BWP is the UL BWP on which the UE may transmit uplinksignal. For a secondary cell (SCell) if configured, the active DL BWPmay be the DL BWP on which the UE may monitor one or more PDCCH andreceive PDSCH when the SCell is activated by receiving a MACactivation/deactivation CE. The active UL BWP is the UL BWP on which theUE may transmit PUCCH (if configured) and/or PUSCH when the SCell isactivated by receiving a MAC activation/deactivation CE. Configurationof multiple BWPs may be used to save UE's power consumption. Whenconfigured with an active BWP and a default BWP, a UE may switch to thedefault BWP if there is no activity on the active BWP. For example, adefault BWP may be configured with narrow bandwidth, an active BWP maybe configured with wide bandwidth. If there is no signal transmitting orreceiving, the UE may switch the BWP to the default BWP, which mayreduce power consumption.

In an example, for each DL BWP or UL BWP in a set of DL BWPs or UL BWPs,respectively, the wireless device may be configured the followingparameters for the serving cell: a subcarrier spacing provided by ahigher layer parameter (e.g., subcarrierSpacing); a cyclic prefixprovided by a higher layer parameter (e.g., cyclicPrefix); a first PRBand a number of contiguous PRBs indicated by a higher layer parameter(e.g., locationAndBandwidth) that is interpreted as RIV, and the firstPRB is a PRB offset relative to the PRB indicated by higher layerparameters (e.g., offsetToCarrier and subcarrierSpacing); an index inthe set of DL BWPs or UL BWPs by respective a higher layer parameter(e.g., bwp-Id); a set of BWP-common and a set of BWP-dedicatedparameters by higher layer parameters (e.g., bwp-Common andbwp-Dedicated).

In an example, switching BWP may be triggered by a DCI or a timer. Whena UE receives a DCI indicating DL BWP switching from an active BWP to anew BWP, the UE may monitor PDCCH and/or receive PDSCH on the new BWP.When the UE receives a DCI indicating UL BWP switching from an activeBWP to a new BWP, the UE may transmit PUCCH (if configured) and/or PUSCHon the new BWP. A gNB may transmit one or more messages comprising a BWPinactivity timer to a UE. The UE starts the timer when it switches itsactive DL BWP to a DL BWP other than the default DL BWP. The UE mayrestart the timer to the initial value when it successfully decodes aDCI to schedule PDSCH(s) in its active DL BWP. The UE may switch itsactive DL BWP to the default DL BWP when the BWP timer expires.

In an example, a BWP may be configured with: a subcarrier spacing, acyclic prefix, a number of contiguous PRBs, an offset of the first PRBin the number of contiguous PRBs relative to the first PRB, or Q controlresource sets if the BWP is a DL BWP.

In an example, on a SCell, there may be no initial active BWP since theinitial access is performed on the PCell. For example, the initiallyactivated DL BWP and/or UL BWP, when the SCell is activated, may beconfigured or reconfigured by RRC signaling. In an example, the defaultBWP of the SCell may also be configured or reconfigured by RRCsignaling.

In an example, gNB may configure UE-specific default DL BWP other thaninitial active BWP after RRC connection, e.g., for the purpose of loadbalancing. The default BWP may support other connected mode operations(besides operations supported by initial active BWP), e.g., fall backand/or connected mode paging. In this case, the default BWP may comprisecommon search space, e.g., at least a search space needed for monitoringa pre-emption indication.

In an example, a DL BWP other than the initial active DL BWP may beconfigured to a UE as the default DL BWP. The reconfiguring the defaultDL BWP may be due to load balancing and/or different numerologiesemployed for active DL BWP and initial active DL BWP.

In an example, for a paired spectrum, DL and UL BWPs may beindependently activated while, for an unpaired spectrum DL and UL BWPSare jointly activated. In case of bandwidth adaptation, where thebandwidth of the active downlink BWP may be changed, there may, in caseof an unpaired spectrum, be a joint activation of a new downlink BWP andnew uplink BWP. For example, a new DL/UL BWP pair where the bandwidth ofthe uplink BWPs may be the same (e.g., no change of uplink BWP).

In an example embodiment, making an association between DL BWP and ULBWP may allow that one activation/deactivation command may switch bothDL and UL BWPs at once. Otherwise, separate BWP switching commands maybe necessary.

In an example, PUCCH resources may be configured in a configured UL BWP,in a default UL BWP and/or in both. For instance, if the PUCCH resourcesare configured in the default UL BWP, UE may retune to the default ULBWP for transmitting an SR. for example, the PUCCH resources areconfigured per BWP or a BWP other than the default BWP, the UE maytransmit an SR in the current active BWP without retuning.

In an example, there may be at most one active DL BWP and at most oneactive UL BWP at a given time for a serving cell. A BWP of a cell may beconfigured with a specific numerology/TTI. In an example, a logicalchannel and/or logical channel group that triggers SR transmission whilethe wireless device operates in one active BWP, the corresponding SR mayremain triggered in response to BWP switching.

In an example, when a new BWP is activated, a configured downlinkassignment may be initialized (if not active) or re-initialized (ifalready active) using PDCCH. In an example, via one or more RRCmessages/signaling, a wireless device may be configured with at leastone UL BWP, at least one DL BWP, and one or more configured grants for acell. The one or more configured grants may be semi-persistentscheduling (SPS), Type 1 grant-free (GF) transmission/scheduling, and/orType 2 GF transmission/scheduling. In an example, one or more configuredgrants may be configured per UL BWP. For example, one or more radioresources associated with one or more configured grants may not bedefined/assigned/allocated across two or more UL BWPs.

In an example, an BWP may be in active during a period of time when aBWP inactivity timer is running. For example, a base station maytransmit a control message to a wireless device to configure a firsttimer value of an BWP inactivity timer. The first timer value maydetermine how long a BWP inactivity timer runs, e.g., a period of timethat a BWP inactivity timer runs. For example, the BWP inactivity timermay be implemented as a count-down timer from a first timer value downto a value (e.g., zero). In an example embodiment, the BWP inactivitytimer may be implemented as a count-up timer from a value (e.g., zero)up to a first timer value down. In an example embodiment, the BWPinactivity timer may be implemented as a down-counter from a first timervalue down to a value (e.g., zero). In an example embodiment, the BWPinactivity timer may be implemented as a count-up counter from a value(e.g., zero) up to a first timer value down. For example, a wirelessdevice may restart a BWP inactivity timer (e.g., UL BWP and/or DL BWPinactivity timers) when the wireless device receives (and/or decodes) aDCI to schedule PDSCH(s) in its active BWP (e.g., its active UL BWP, itsactive DL BWP, and/or UL/DL BWP pair).

FIG. 28 shows example of BWP switching mechanism. A UE may receive RRCmessage comprising parameters of a SCell and one or more BWPconfiguration associated with the SCell. Among the one or more BWPs, atleast one BWP may be configured as the first active BWP (e.g., BWP 1 inFIG. 28), one BWP as the default BWP (e.g., BWP 0 in FIG. 28). The UEmay receive a MAC CE to activate the SCell at the n^(th) slot. The UEmay start the sCellDeactivationTimer, and start CSI related actions forthe SCell, and/or start CSI related actions for the first active BWP ofthe SCell at the (n+x)^(th) slot. The UE may start the BWP inactivitytimer at the (n+x+k)^(th) slot in response to receiving a DCI indicatingswitching BWP from BWP 1 to BWP 2. When receiving a PDCCH indicating DLscheduling on BWP 2, for example, at the (n+x+k+m)^(th) slot, the UE mayrestart the BWP inactivity timer. The UE may switch back to the defaultBWP (e.g., BWP 0) as an active BWP when the BWP inactivity timerexpires, at the (n+x+k+m+l)^(th) slot. The UE may deactivate the SCellwhen the sCellDeactivationTimer expires.

In an example, a BWP inactivity timer may be applied in a PCell. A basestation may transmit one or more RRC messages comprising a BWPinactivity timer to a wireless device. The wireless device may start theBWP inactivity timer if the wireless devices switches its active DL BWPto a DL BWP other than the default DL BWP on the PCell. The wirelessdevice may restart the BWP inactivity timer if it successfully decodes aDCI to schedule PDSCH(s) in its active DL BWP. The wireless device mayswitch its active DL BWP to the default DL BWP if the BWP inactivitytimer expires.

In an example, employing the BWP inactivity timer may reduce UE's powerconsumption when the UE is configured with multiple BWPs on a cell (aPCell or a SCell). The UE may switch to a default BWP on the PCell orSCell when there is no activity on an active BWP (e.g., when the BWPinactivity timer expires).

In an example, a gNB may transmit one or more RRC message comprising oneor more CSI configuration parameters comprising at least: one or moreCSI-RS resource settings; one or more CSI reporting settings, and oneCSI measurement setting.

In an example, a CSI-RS resource setting may comprise one or more CSI-RSresource sets. In an example, there may be one CSI-RS resource set forperiodic CSI-RS, or semi-persistent (SP) CSI-RS. In an example, a CSI-RSresource set may comprise at least one of: one CSI-RS type (e.g.,periodic, aperiodic, or semi-persistent); one or more CSI-RS resourcescomprising at least one of: CSI-RS resource configuration identity (orindex); number of CSI-RS ports; CSI-RS configuration (symbol and RElocations in a subframe); CSI-RS subframe configuration (subframelocation, offset, and/or periodicity in radio frame); CSI-RS powerparameter; CSI-RS sequence parameter; CDM type parameter; frequencydensity; transmission comb; and/or QCL parameters.

In an example, one or more CSI-RS resources may be transmittedperiodically, using aperiodic transmission, using a multi-shottransmission, and/or using a SP transmission. In a periodictransmission, the configured CSI-RS resource may be transmitted using aconfigured periodicity in time domain. In an aperiodic transmission, theconfigured CSI-RS resource may be transmitted in a dedicated time slotor subframe. In a multi-shot or SP transmission, the configured CSI-RSresource may be transmitted within a configured period. In an example, agNB may transmit one or more SP CSI-RSs with a periodicity. The gNB maystop transmission of the one or more SP CSI-RSs if the CSI-RS isconfigured with a transmission duration. The gNB may stop transmissionof the one or SP CSI-RSs in response to transmitting a MAC CE or DCI fordeactivating (or stopping the transmission of) the one or more SPCSI-RSs.

In an example, a CSI reporting setting may comprise at least one of: onereport configuration identifier; one report type; one or more reportedCSI parameter(s); one or more CSI type (e.g., type I or type II); one ormore codebook configuration parameters; one or more parametersindicating time-domain behavior; frequency granularity for CQI and PMI;and/or measurement restriction configurations. The report type mayindicate a time domain behavior of the report (aperiodic, SP, orperiodic). The CSI reporting setting may further comprise at least oneof: one periodicity parameter; one duration parameter; and/or one offset(e.g., in unit of slots), if the report type is a periodic or SP report.The periodicity parameter may indicate a periodicity of a CSI report.The duration parameter may indicate a duration of CSI reporttransmission. The offset parameter may indicate value of timing offsetof CSI report.

In an example, a CSI measurement setting may comprise one or more linkscomprising one or more link parameters. The link parameter may compriseat least one of: one CSI reporting setting indication, CSI-RS resourcesetting indication, and one or more measurement parameters.

FIG. 29 shows example of various CSI report triggering mechanisms. In anexample, a gNB may trigger a CSI reporting by transmitting an RRCmessage, or a MAC CE, or a DCI, as shown in FIG. 29. In an example, a UEmay perform periodic CSI reporting (e.g., P-CSI reporting in FIG. 29)based on an RRC message and one or more periodic CSI-RSs. In an example,a UE may not be allowed (or required) to perform periodic CSI reportingbased on one or more aperiodic CSI-RSs and/or one or more SP CSI-RSs. Inan example, a UE may perform SP CSI reporting (e.g., SP-CSI reporting inFIG. 29) based on a MAC CE and/or a DCI and based on one or moreperiodic or SP CSI-RSs. In an example, a UE may not be allowed (orrequired) to perform SP CSI reporting based on one or more aperiodicCSI-RSs. In an example, a UE may perform aperiodic CSI reporting (e.g.,Ap-CSI reporting in FIG. 29) based on a DCI and based on one or moreperiodic, SP, or aperiodic CSI-RSs. In an example, a wireless device mayperform a SP CSI reporting on a PUCCH in response to the SP CSIreporting being activated (or triggered) by a MAC CE. The wirelessdevice may perform a SP CSI reporting on a PUSCH in response to the SPCSI reporting being activated (or triggered). In an example, a basestation may instruct (e.g., by transmitting the MAC CE) a wirelessdevice to perform SP CSI reporting on PUCCH when a compact CSI (e.g.,small amount of report contents) is required by the base station, or DCItransmission is not convenient for the base station, and/or the CSI isnot urgently required by the base station. In an example, a base stationmay instruct (e.g., by transmitting the DCI) a wireless device toperform SP CSI reporting on PUSCH when a large-sized CSI (e.g., bigamount of report contents) is required by the base station, or a DCItransmission is convenient for the base station, and/or the CSI isurgently required by the base station.

FIG. 30 shows an example of SP CSI reporting in a cell. In an example, abase station (e.g., gNB in FIG. 30) may transmit to a wireless device(e.g., UE in FIG. 30) one or more RRC messages comprising configurationparameters of one or more SP CSI reporting configurations. The basestation may transmit to the wireless device, at slot (or subframe) n, a1^(st) MAC CE or DCI indicating an activation of a SP CSI reportingconfiguration of the one or more SP CSI reporting configurations. Thebase station may start transmitting one or more SP CSI-RSs at slot (orsubframe) n+k. In an example, k may be zero or an integer greater thanzero, configured by an RRC message, or be predefined as a fixed value.

As shown in FIG. 30, after or in response to receiving the 1^(st) MAC CEor the 1^(st) DCI, the wireless device may perform CSI measurements onone or more CSI-RSs according to the activated SP CSI reportingconfiguration. In an example, after or in response to receiving the1^(st) MAC CE or the 1^(st) DCI, the wireless device may transmit one ormore SP CSI reports (e.g., based on the CSI measurements) atslot/subframe n+k+m, n+k+m+l, n+k+m+2*l, etc., with a periodicity of 1subframes (or slots). The periodicity may be configured in an RRCmessage. In an example, the UE may receive a 2^(nd) MAC/DCI indicating adeactivation of the SP CSI reporting configuration. After receiving the2^(nd) MAC/DCI, or in response to the 2^(nd) MAC/DCI, the UE may stoptransmitting the one or more SP CSI reports. In an example, k may bezero (configured, or predefined). In an example, m (e.g., when k=0) maybe a time offset between the wireless device receives the 1^(st) MACCE/DCI for activation of the SP CSI reporting and the wireless devicetransmits a first SP CSI report of the one or more SP CSI reports. In anexample, m may be configured by an RRC message, or be predefined as afixed value. A value of m may depend on the capability of a UE and/orthe network.

As shown in FIG. 30, a wireless device may assume a CSI-RS transmissionperiod (e.g., CSI-RS transmission Window in FIG. 30), in response to a1^(st) MAC CE/DCI for activation of a SP CSI reporting configuration andbased on one or more configuration parameters of the activated SP CSIreporting configuration. The base station may transmit one or moreCSI-RSs at least in the CSI-RS transmission period, based on theactivated SP CSI reporting configuration. In an example, the wirelessdevice may perform CSI measurements on the one or more CSI-RSstransmitted in the CSI-RS transmission period.

In existing technologies, a base station may transmit a DCI to a UE totrigger a Semi-Persistent Scheduling (SPS) assignment for some types(e.g., VoIP, V2X) of data transmission. When the UE receives the DCItriggering the SPS assignment for downlink transmission or uplinktransmission, the UE may keep receiving downlink packets via a PDSCH orkeep transmitting uplink packets via a PUSCH. The PDSCH or the PUSCH maybe indicated in the DCI. By doing so, the base station may reducedownlink signaling transmission for some types of data transmission.

FIG. 31 shows example of the embodiment, where, a gNB may trigger a SPS(e.g., for downlink transmission) or type 2 grant-free (GF, e.g., foruplink transmission) activation by transmitting a DCI at subframe n. Inorder to differentiate from normal dynamic scheduling, the DCI may beCRC scrambled by a first RNTI (e.g., SPS C-RNTI for downlinktransmission or CS-RNTI for uplink transmission) different from a secondRNTI for normal dynamic scheduling (e.g., C-RNTI). In an example, a gNBmay transmit one or more DCI via a PDCCH for uplink data scheduling.When receiving a first DCI with CRC scrambled by a first RNTI, the UEmay consider a PUSCH assignment indicated by the first DCI is forSPS/type 2 GF scheduling. The UE may transmit uplink data via the PUSCHin multiple subframes, with a configured periodicity. When receiving asecond DCI with CRC scrambled by the second RNTI, the UE may consider aPUSCH assignment indicated by the second DCI is for dynamic scheduling.The UE may transmit uplink data via the PUSCH in a subframe. Thesubframe may be indicated by the second DCI, or a subframe after apredefined subframes when receiving the second DCI.

In an example, as shown in FIG. 31, abase station (e.g., gNB in FIG. 31)transmits to a wireless device (e.g., UE in FIG. 31) one or more RRCmessages comprising configuration parameters of a type 2 GFtransmission. The base station may transmit to the wireless device afirst DCI indicating activation of the type 2 GF transmission (e.g., atslot/subframe n as shown in FIG. 31). The UE may transmit, in responseto the first DCI, uplink data packets (e.g., from slot/subframe n+m asshown in FIG. 31) for the activated type 2 GF with a transmissionperiodicity on PUSCH indicated by an RRC message or the first DCI. TheUE may keep transmitting uplink data packets with a periodicityassociated with the activated type 2 GF (e.g., at subframe n+m+l,n+m+2*1 . . . , as shown in FIG. 31). The base station may transmit tothe wireless device a second DCI indicating deactivation of the type 2GF. The wireless device may stop, in response to the second DCI, thetransmissions of the uplink data packets.

In general, a HARQ procedure may apply for a SPS/type 2 GF transmission,to guarantee a gNB correctly receive the data. As shown in FIG. 31, thebase station may transmit a third DCI indicating retransmission of anuplink data packet (e.g., at subframe n+k). In an example, in order todifferentiate the DCI for indicating activation/deactivation of a type 2GF transmission from indicating a retransmission of the uplink datapacket, the base station may transmit the second DCI indicating, bysetting a first field of the second DCI to a first value, that a lastPUSCH transmission for the uplink data packet is not correctly received.For example, the first field may be a new data indicator (e.g., NDI).The gNB may indicate an uplink data packet transmission is not correctlyreceived and request a UE to retransmit the uplink data packet, bysetting the NDI to 1 (e.g., for 1-bit NDI field), and a HARQ processnumber to a value associated with the uplink data packet forretransmission. When the UE receives the second DCI for indicatingretransmission, the UE may retransmit the uplink data packet associatedwith the HARQ process number via a PUSCH. The PUSCH may be indicated bythe second DCI.

In general, a base station may use, one or more fields of a DCI, and/orCRC of the DCI, to indicate a SPS/type 2 GF activation/deactivation,and/or retransmission of the activated SPS/type 2 GF data. In order todifferentiate whether the DCI is for activation or deactivation, orretransmission of a SPS/type 2 GF data, the gNB may set one or morefields of the DCI indicating activation, deactivation, orretransmission.

In an example, the one or more fields of the DCI may comprise at leastone of: a TPC for PUSCH; an NDI field; an MCS field; a HARQ processnumber field; a resource assignment (RA) field; and/or a redundancyversion (RV) field. An NDI field may indicate whether there is new data.A HARQ process number may identify a HARQ process associated with aPUSCH transmission of a transmission block. A RV field may indicate theredundancy version in case of retransmission. An MCS field comprising atleast a Most Significant Bit (MSB, e.g., the first bit in the left ofthe MCS field) may indicate a modulation and code scheme for the PUSCHtransmission.

In an example, a base station may use, one or more fields of a DCI,and/or CRC of the DCI, to indicate a SPS/type 2 GFactivation/deactivation, and/or retransmission of the activated SPS/type2 GF data. The base station may set the NDI field to ‘1’ indicating aDCI is for retransmission of a SPS data, when the DCI is CRC scrambledby a CS-RNTI (or SPS C-RNTI). In an example, the base station may setthe NDI field to ‘0’ indicating the DCI is for activation/deactivationof the SPS transmission, when the DCI is CRC scrambled by the CS-RNTI(or SPS C-RNTI). In an example, the base station may indicate whetherthe DCI is for activation or deactivation by setting one or more fieldsof the DCI, in addition to setting the NDI field. In an example, thebase station may transmit a PDCCH with a DCI indicating activation ofthe SPS/type 2 GF uplink transmission by setting the TPC field to afirst value (e.g., ‘00’ for a 2-bit TPC field), the MSB bit of the MCSand RV field to a second value (e.g., ‘0’) in the DCI (e.g., DCI format0), for a first DCI format (e.g., DCI format 0). In an example, the basestation may transmit a PDCCH with a DCI indicating activation of theSPS/type 2 GF transmission by setting the TPC field to a first value(e.g., ‘00’), the RV field to a second value (e.g., ‘00’), and the HARQprocess number to a third value (e.g., ‘000’) in the DCI, for a secondDCI format (e.g., DCI format 6-0A). In an example, the first DCI format(e.g., DCI format 0) may be transmitted on a first PDCCH. The second DCIformat (e.g., DCI format 6-0A) may be transmitted on a second PDCCH(e.g., MPDCCH). The first PDCCH may be different from the second PDCCH,at least on transmit format, radio resource for the transmission, sincethe second PDCCH is for an MTC UE which may be located in a deepcoverage area and have a limited receiving capacity, the first PDCCH isfor a normal UE which may be in a normal coverage area, and have normalreceiving capacity. When a UE receives a DCI scrambled by the SPS C-RNTIor CS-RNTI, the UE may perform a validation of the PDCCH to determinewhether the DCI is for activation, if the NDI field is set to 0. In anexample, The UE may not perform a validation of the PDCCH, if the NDIfield is set to 1. In this case, the UE may perform a retransmissionaccording to the DCI.

In an example, when performing a PDDCH validation for a first DCI format(e.g., DCI format 0), if the TPC command is the first value (e.g.,‘00’), the MSB bit of the MCS and RV field is the second value (e.g.,‘0’) in a received DCI, the UE may consider the received DCI informationaccordingly as a valid SPS/type 2 GF activation. In response to the DCIbeing a valid SPS/type 2 GF activation, the UE may activate the SPS/type2 GF and/or transmit uplink data packet according to the DCI. In anexample, when performing a PDCCH validation for the second DCI format(e.g., DCI format 6-0A), if the TPC command is ‘00’, the RV field is‘00’ and the HARQ process number is ‘000’ in the received DCI, the UEmay consider the received DCI information accordingly as a validSPS/type 2 GF activation. In response to the DCI being a valid SPS/type2 GF activation, the UE may transmit uplink data packets according tothe DCI.

In an example, when performing a PDCCH validation, the UE may consider areceived DCI information accordingly as an invalid SPS/type 2 GFactivation, if the TPC command is not a ‘00’, and/or the MSB bit of theMCS and RV field is not a ‘0’ in the received DCI, for DCI format 0. Inan example, when performing the PDCCH validation, the UE may considerthe received DCI information accordingly as an invalid SPS/type 2 GFactivation, if the TPC command is not a ‘00’, and/or the RV field is nota ‘00’, and/or the HARQ process number is not a ‘000’ in the receivedDCI, for DCI format 6-0A. In response to the DCI being an invalidSPS/type 2 GF activation, the UE may consider the DCI format has beenreceived with a non-matching CRC. In an example, the UE may discard theDCI, and/or not perform actions indicated by the DCI, in response to thereceived DCI being with a non-matching CRC.

In an example, the gNB may transmit a PDCCH with a DCI indicatingdeactivation of the SPS/type 2 GF transmission by setting the TPCcommand to ‘00’, the MCS and RV field to ‘11111’, the Cyclic shift DM RSfield to ‘000’ if present, and the RA and hopping field to all ‘1’s inthe DCI (e.g., DCI format 0), for a normal UE. In an example, the gNBmay transmit a PDCCH with a DCI indicating deactivation of the SPS/type2 GF transmission by setting the TPC command to ‘00’, the RV field to‘00’, the repetition number to ‘00’, the MCS field to ‘1111’, the RAfield to all ‘1’s and a HARQ process number to ‘000’ in the DCI (e.g.,DCI format 6-0A), for a MTC UE. When a UE receive a DCI scrambled by theSPS C-RNTI or CS-RNTI, the UE may perform a validation of the PDCCH todetermine whether the DCI is for deactivation, if the NDI field is setto ‘0’. In an example, The UE may not perform a validation of the PDCCH,if the NDI field is set to ‘1’. In this case, the UE may perform aretransmission according to the DCI.

In an example, when performing a PDCCH validation for DCI format 0, ifthe TPC command is ‘00’, the MCS and RV field is ‘11111’, the Cyclicshift DM RS field is ‘000’ if present, and the RA and hopping field isset to all ‘1’s, in a received DCI, the UE may consider the received DCIinformation accordingly as a valid SPS/type 2 GF deactivation. Inresponse to the DCI being a valid SPS/type 2 GF deactivation, the UE maystop transmission of the uplink data packets or stop receiving downlinkdata packets. In an example, when performing a PDCCH validation for DCIformat 6-0A, if the TPC command is ‘00’, the RV field is ‘00’, therepetition number is ‘00’, the MCS field is ‘1111’, the RA field is setto all ‘1’s, and the HARQ process number is ‘000’, in the received DCI,the UE may consider the received DCI information accordingly as a validSPS/type 2 GF deactivation. In response to the DCI being a validSPS/type 2 GF deactivation, the UE may stop transmission of the uplinkdata packets or stop receiving downlink data packets.

In an example, when performing the PDCCH validation, the UE may considerthe received DCI information accordingly as an invalid SPS/type 2 GFdeactivation, if the TPC command is not ‘00’, and/or the MCS and RVfield is not ‘11111’, and/or the cyclic shift DM RS field is not ‘000’if present, and/or the RA and hopping field is not set to all ‘1’s, inthe received DCI, for DCI format 0. In an example, when performing thePDCCH validation, the UE may consider the received DCI informationaccordingly as an invalid SPS/type 2 GF activation, if the TPC commandis not ‘00’, and/or the RV field is not ‘00’, and/or the repetitionnumber is not ‘00’, and/or the MCS field is not ‘1111’, and/or the RAfield is not set to all ‘1’s, and/or the HARQ process number is not‘000’, in the received DCI, for DCI format 6-0A. In response to the DCIbeing an invalid SPS/type 2 GF deactivation, the UE may consider the DCIformat has been received with a non-matching CRC. In an example, the UEmay skip the DCI in response to the received DCI being with anon-matching CRC.

In an example, when there is a big amount of transmission blocks (TBs)to be transmitted to a UE and/or the UE is in a changing channelcondition, a UE may transmit frequent CSI reports to a base station forfacilitating downlink channel scheduling. In an example, aperiodic CSIreport may not be efficient in this case, where the UE may transmit theaperiodic CSI report in one shot. The aperiodic CSI report may betriggered by a DCI. Request for multiple and/or frequent CSI reports maybe achieved by transmitting multiple DCIs, which may increase DCItransmission and reduce the capacity of PDCCH. In an example, periodicCSI report may not work efficient or convenient in this case. Theperiodic CSI report may be configured or reconfigured in an RRC message.An RRC message for the periodic CSI report may not be efficient toenable or disable the frequent CSI reports. A DCI basedactivation/deactivation mechanism may be efficient and/or convenient forfrequent CSI reports when there is a big amount of transmission blocks(TBs) to be transmitted to a UE and/or the UE is in a changing channelcondition. CSI reports based on activation/deactivation of a DCI may beSP CSI reports. Example embodiments improve efficiency of downlinktransmission, batter power consumption for SP CSI report.

In an example, it may be straightforward or obvious that a DCI basedmechanism of SPS/type 2 GF activation/deactivation (A/D) in LTE systemmay apply in a case when a DCI is used to indicate A/D of SP CSIreporting. There are several differences between SPS/type 2 GFtransmission and SP CSI reports which may result in inefficiency orextra complexity in the UE when a base station and/or a UE applies themechanism of SPS/type 2 GF A/D for SP CSI report A/D.

In an example, a SP CSI report A/D may be different from a SPS/type 2 GFA/D, e.g., on retransmission mechanism. A HARQ based retransmissionmechanism may not be applied in SP CSI report, compared with SPS/type 2GF transmission. In the case, a UE may not check whether the DCI is forretransmission or for deactivation of the activated SP CSI report.Implementing the same mechanism of SPS/type 2 GF A/D may increaseimplementation complexity and/or power consumption at the UE whenperforming validation of a PDCCH for A/D of a SP CSI report. Exampleembodiments provides mechanisms to improve implementation complexityand/or power consumption of the UE for the SP CSI report.

In an example, a SP CSI report A/D may be different from a SPS/type 2 GFA/D, e.g., on power control mechanism. In LTE system, a base station maytransmit a DCI for triggering type 2 GF transmission by setting the TPCfield (e.g., if the DCI comprises the TPC field) of the DCI to apredefined value (e.g., 0 or 00). In this case, the TPC field, afterbeing set to a predefined value may not indicate a power command for theuplink data transmission via a PUSCH. The UE may determine thetransmission power according to the RRC message. In an example, whentransmitting the SP CSI reports, the UE may transmit the SP CSI reportswith uplink data packets on a PUSCH. Transmission power of the uplinkdata packets and/or the SP CSI reports may be indicated in a TPC fieldin a SP CSI A/D DCI. In an example, the TPC field may not be allowed toset to a predefined value (e.g., 0 or 00) when the DCI is used foractivating the SP CSI reporting. Implementing the same mechanism ofSPS/type 2 GF A/D may result in incorrect (e.g., less than required orover than required) transmission power determination of the SP CSIreport transmission via the PUSCH. Example embodiments providesmechanisms to improve transmission power determination accuracy of theUE for the SP CSI report transmission via a PUSCH. Example embodimentsprovides mechanisms to improve uplink interference to other UEs orimprove efficiency of uplink transmission when transmitting a SP CSIreport via a PUSCH. Example embodiments provides mechanisms to improveimplementation complexity and/or power consumption of the UE for the SPCSI report.

FIG. 32 shows an example embodiment of SP CSI report A/D mechanism. Inan example, a base station (e.g., gNB in FIG. 32) transmits to awireless device (e.g., UE in FIG. 32) one or more RRC messagescomprising configuration parameters of SP CSI reporting, wherein, theconfiguration parameters comprising at least one of: a first radionetwork temporary identifier (e.g., SP-CSI-RNTI as shown in FIG. 32);and at least one or more SP CSI reporting settings.

In an example, the one or more RRC messages may comprise configurationparameters of one reference signal (RS) resource setting. The RSresource setting may comprise a set of RS resources, wherein, a RSresource may be associated with: a RS resource configuration identifier;radio resource configuration (e.g., number of ports; time and frequencyresource allocation; frequency density; etc.). In an example, the RS maybe a CSI-RS, and/or a SS block.

In an example, a SP CSI report setting may comprise a set of SP CSIreport parameters comprising at least one of: a SP CSI reportidentifier; and/or one or more parameters for SP CSI reportingcomprising at least one of: a CSI type (e.g., Type I or Type II); areport quantity indicator (e.g., indicating a CSI-related quantity toreport, or a L1-RSRP related quantity to report, etc.); a reportconfiguration type (e.g., indicating the time domain behavior of thereport—either aperiodic, semi-persistent, or periodic); a valueindicating frequency granularity for CSI report; parameters indicatingperiodicity and slot offset of CSI report.

In an example, the one or more RRC messages may further compriseparameters indicating multiple trigger states for SP CSI reports onPUSCH. In an example, a SP CSI report trigger state may comprise atleast one of: a SP CSI report trigger index; a RS resource configurationidentifier; and/or a SP CSI report identifier. The RS resourceconfiguration identifier may indicate a RS resource associated with a SPCSI report. The SP CSI report identifier may indicate parameters for theSP CSI report.

In an example, the UE may receive a first DCI (e.g., 1^(st) DCI in FIG.32) via a PDCCH, wherein the first DCI may comprise at least one of: aTPC for PUSCH; a NDI field; a MCS field; a HARQ process number field; aRA field; a RV field; a CSI request field; a first downlink assignmentindex; a second downlink assignment index; a first parameter indicatinguplink precoding information and number of layers if present; a secondparameter indicating antenna ports; and/or a third parameter indicatingCBG transmission information if present.

In an example, in response to or after receiving the first DCI, the UEmay perform PDCCH validation for a SP CSI activation orrelease/deactivation, based on at least one of: CRC parity bits of thefirst DCI; one or more fields of the first DCI being set to predefinedvalues.

In an example, the UE may determine the PDCCH validation for anactivation of a SP CSI report is achieved in response to: the CRC paritybits of the first DCI being scrambled by the first RNTI (e.g., theSP-CSI-RNTI); the HARQ process number field being set to all ‘0’s;and/or the RV field being set to “00”. In response to the validation ofthe PDCCH being achieved for activation of the SP CSI report, the UE maytransmit via a radio resource of PUSCH, the SP CSI report associatedwith a SP CSI report trigger index with a transmission periodicity inmultiple subframes/slots. The radio resource of the PUSCH may beindicated in the RA field of the first DCI. The SP CSI report triggerindex may be indicated in the CSI request field of the first DCI. Thetransmission periodicity may be configured in the at least one messages.In response to the validation of the PDCCH being achieved for activationof the SP CSI report, the UE may determine a RS resource indicated bythe RS resource configuration identifier associated with the SP CSIreport trigger index. The UE may measure CSI parameters indicated by theSP CSI report identifier associated with the SP CSI report triggerindex. The UE may transmit SP CSI reports based on the measured CSIparameters on the PUSCH in multiple subframes/slots, starting from afirst subframe/slot. In an example, the first subframe/slot may be afirst available PUSCH subframe/slot after the subframe/slot whenreceiving the first DCI. In an example, the first subframe/slot may bean offset to the subframe/slot when receiving the first DCI. In anexample, the offset may be indicated by the first DCI, or configured bythe RRC message, or a predefined (or fixed) value. In an example, the UEmay determine a transmission power for the SP CSI report via the PUSCHaccording to the TPC field of the first DCI. In an example, the TPCfield (e.g., for PUSCH) of the first DCI may indicate power control ofthe SP CSI report transmission on the PUSCH. The TPC field may not beset to a predefined value for indicating activation/deactivation of theSP CSI report.

In an example, the UE may determine the PDCCH validation for anactivation of a SP CSI report is not achieved in response to at leastone of: the CRC parity bits of the first DCI not being scrambled by thefirst RNTI (e.g., the SP-CSI-RNTI); the HARQ process number field notbeing set to all ‘0’s; and/or the RV field not being set to “00”. Inresponse to the validation of the PDCCH not being achieved foractivation of the SP CSI report, the UE may consider the first DCI ashaving been detected with a non-matching CRC. In response to thevalidation of the PDCCH not being achieved for activation of the SP CSIreport, the UE may ignore the first DCI received on the PDCCH, or notperform actions according to the first DCI, or not perform actionsrelated to SP CSI report according to the first DCI.

By the example embodiment, not setting the TPC field to a predefinedvalue may allow a base station flexibly control transmission power of aUE for SP CSI report. By the example embodiment, not checking NDI fieldfor SP CSI activation/deactivation may reduce implementation complexityof a UE for SP CSI report. Example embodiments may improve transmissionpower determination accuracy of the UE for the SP CSI reporttransmission via a PUSCH. Example embodiments may improve uplinkinterference to other UEs or improve efficiency of uplink transmissionwhen transmitting a SP CSI report via a PUSCH. Example embodiments mayimprove implementation complexity and/or power consumption of the UE forthe SP CSI report.

In an example, the UE may receive a second DCI (e.g., 2^(nd) DCI in FIG.32) via the PDCCH, wherein the second DCI may comprise at least one of:a TPC for PUSCH; a NDI field; a MCS field; a HARQ process number field;a RA field; a RV field; a CSI request field; a first downlink assignmentindex; a second downlink assignment index; a first parameter indicatinguplink precoding information and number of layers if present; a secondparameter indicating antenna ports; and/or a third parameter indicatingCBG transmission information if present.

In an example, in response to or after receiving the second DCI, the UEmay perform PDCCH validation for a SP CSI activation orrelease/deactivation, based on at least one of: CRC parity bits of thesecond DCI; one or more fields of the second DCI being set to predefinedvalues.

In an example, the UE may determine the PDCCH validation for adeactivation of a SP CSI report is achieved in response to: the CRCparity bits of the second DCI being scrambled by the first RNTI (e.g.,the SP-CSI-RNTI); the HARQ process number field being set to all ‘0’s;and/or the RV field being set to “00”; the MCS field being set to all‘1’s; and/or the RA field being set to a predefined value (e.g., all‘0’s or all ‘1’s). In response to the validation of the PDCCH beingachieved for deactivation of the SP CSI report, the UE may stop thetransmissions of the SP CSI report associated with a SP CSI reporttrigger index. The SP CSI report trigger index may be indicated in theCSI request field of the second DCI.

In an example, the UE may determine the PDCCH validation fordeactivation of a SP CSI report is not achieved in response to at leastone of: the CRC parity bits of the second DCI not being scrambled by thefirst RNTI (e.g., the SP-CSI-RNTI); the HARQ process number field notbeing set to all ‘0’s; and/or the RV field not being set to “00”; theMCS field not being set to all ‘1’s; and/or the RA field not being setto a predefined value (e.g., all ‘0’s or all ‘1’s). In response to thevalidation of the PDCCH not being achieved for deactivation of the SPCSI report, the UE may consider the second DCI as having been detectedwith a non-matching CRC. In response to the validation of the PDCCH notbeing achieved for deactivation of the SP CSI report, the UE may ignorethe second DCI received on the PDCCH, or not perform actions accordingto the first DCI. In response to the validation of the PDCCH not beingachieved for deactivation of the SP CSI report, the UE may keeptransmitting the SP CSI report.

By the example embodiment, not setting the TPC field to a predefinedvalue may allow a base station flexibly control transmission power of aUE for uplink data packets, when deactivating a SP CSI report. By theexample embodiment, not checking NDI field for SP CSIactivation/deactivation may reduce implementation complexity of a UE forSP CSI report. Example embodiments may improve transmission powerdetermination accuracy of the UE for a PUSCH transmission. Exampleembodiments may improve uplink interference to other UEs or improveefficiency of uplink transmission via a PUSCH. Example embodiments mayimprove implementation complexity and/or power consumption of the UE.

FIG. 33 shows an example flowchart of the embodiment for SP CSIactivation. In an example, a wireless device may receive at least an RRCmessage comprising configuration of a SP CSI report and a RNTI value(e.g., a SP-CSI-RNTI as shown in FIG. 33). The wireless device mayreceive a DCI via a PDSCH. In response to or after receiving the DCI,the wireless device may perform validation of the DCI for activation ofthe SP CSI report based on the RNTI value and one or more fields of theDCI. The one or more fields may comprise a HARQ process number and a RVfield. The wireless device may determine whether the validation isachieved or not based on the RNTI value and the one or more fields. Inan example, the wireless device may determine the validation foractivation of the SP CSI report is achieved in response to: CRC paritybits of the DCI being scrambled by the SP-CSI-RNTI; the HARQ processnumber being set to a first predefined value (e.g., all ‘0’s); and theRV field being set to a second predefined value (e.g., ‘00’). Inresponse to the validation for activation of the SP CSI report beingachieved, the wireless device may transmit the SP CSI report via a PUSCHwith a transmission power determined based on a power control command inthe DCI.

In an example, a wireless device may determine a transmission power fora PUSCH transmission (e.g., comprising an uplink data transmissionand/or CSI report) in subframe i for a serving cell c may be given by anequation:

${P_{{PUSCH},c}(i)} = {\min\begin{Bmatrix}{{P_{{CMAX},c}(i)},} \\{{10{\log_{10}\left( {M_{{PUSCH},c}(i)} \right)}} + {P_{{O\_{PUSCH}},c}(j)} + {{\alpha_{c}(j)} \cdot {PL}_{c}} + {\Delta_{{TF},c}(i)} + {f_{c}(i)}}\end{Bmatrix}{\quad{\lbrack{dBm}\rbrack.}}}$wherein P_(CMAX,c)(i) may be a configured transmission power of thewireless device in subframe i for the serving cell c. M_(PUSCH,c)(i) maybe a bandwidth of the PUSCH resource assignment expressed in number ofresource blocks valid for subframe i and the serving cell c, and/orPL_(c) may be a downlink pathloss estimate for the wireless deviceserving cell c in dB. P_(O_PUSCH) may be a target received power valueconfigured in an RRC message. α may be a power compensation factorconfigured in the RRC message. A may be a power offset value. MO may bea power control adjustment state and be equal to a sum of f_(c)(i−1) anda power control command. The power control command may be indicated bythe TPC of the DCI.

In an example, the wireless device may determine the validation foractivation of the SP CSI report is not achieved in response to at leastone of: CRC parity bits of the DCI not being scrambled by theSP-CSI-RNTI; the HARQ process number not being set to the firstpredefined value; and the RV field not being set to the secondpredefined value. In response to the validation for activation of the SPCSI report not being achieved, the wireless device may consider the DCIas having been detected with a non-matching CRC.

FIG. 34 shows an example flowchart of the embodiment for SP CSIdeactivation. In an example, a wireless device may receive at least anRRC message comprising configuration of a SP CSI report and a RNTI value(e.g., a SP-CSI-RNTI as shown in FIG. 34). The wireless device mayreceive a DCI via a PDSCH. In response to or after receiving the DCI,the wireless device may perform validation of the DCI for deactivationof the SP CSI report based on the RNTI value and one or more fields ofthe DCI. The one or more fields may comprise a HARQ process number; a RVfield; an MCS field; and/or a resource assignment field. The wirelessdevice may determine whether the validation is achieved or not based onthe RNTI value and the one or more fields. In an example, the wirelessdevice may determine the validation for deactivation of the SP CSIreport is achieved in response to: CRC parity bits of the DCI beingscrambled by the SP-CSI-RNTI; the HARQ process number being set to afirst predefined value (e.g., all ‘0’s); the RV field being set to asecond predefined value (e.g., ‘00’); the MCS field being set to a thirdpredefined value (e.g., all ‘1’s); and/or the resource assignment fieldbeing set to a fourth predefined value (e.g., all ‘0’s or all ‘1’s). Inresponse to the validation for deactivation of the SP CSI report beingachieved, the wireless device may stop transmission of the SP CSI reportvia a PUSCH.

In an example, the wireless device may determine the validation fordeactivation of the SP CSI report is not achieved in response to atleast one of: CRC parity bits of the DCI not being scrambled by theSP-CSI-RNTI; the HARQ process number not being set to the firstpredefined value; the RV field not being set to the second predefinedvalue; the MCS field not being set to a third predefined value (e.g.,all ‘1’s); and/or the resource assignment field not being set to afourth predefined value (e.g., all ‘0’s or all ‘1’s). In response to thevalidation for activation of the SP CSI report not being achieved, thewireless device may consider the DCI as having been detected with anon-matching CRC.

In an example, when receiving a DCI, a UE may perform validation of aPDCCH for SP CSI report activation/deactivation based on at least oneof: CRC parity bits of the DCI; the NDI field of the DCI; and/or the atleast second field of the DCI.

In an example, when the CRC parity bits of the DCI is scrambled by theSP-CSI-RNTI, the UE may determine the PDCCH is for activation of a SPCSI reporting, or deactivation of a SP CSI reporting, based on the NDIfield of the DCI. In an example, the UE may perform validation of thePDCCH based on the NDI field. In an example, the validation of the PDCCHis to check whether the PDCCH is for activation, or deactivation of a SPCSI reporting. In an example, the UE may determine the PDCCH is foractivation of a SP CSI reporting, if the NDI field is set to a firstvalue (e.g., ‘0’ or ‘1’ for a 1-bit NDI field). In response to the PDCCHbeing for activation of a SP CSI report, the UE may determine a RSresource indicated by the RS resource configuration identifierassociated with the SP CSI report trigger index. The UE may measure CSIparameters indicated by the SP CSI report identifier associated with theSP CSI report trigger index. The UE may transmit SP CSI reports based onthe measured CSI parameters on the PUSCH in multiple subframes (orslot), starting from a first subframe (or slot). In an example, thefirst subframe (or slot) may be a first available PUSCH subframe (orslot) after the subframe (or slot) when receiving the DCI. In anexample, the first subframe (or slot) may be an offset to the subframe(or slot) when receiving the DCI. In an example, the offset may beindicated by the DCI, or configured by the RRC message, or a predefined(or fixed) value. In an example, the UE may determine the PDCCH is fordeactivation of a SP CSI reporting, if the NDI field is set to a secondvalue (e.g., ‘0’ or ‘1’ for a 1-bit NDI field). The second value may bedifferent from the first value. In response to the PDCCH being fordeactivation of a SP CSI report, the UE may stop transmitting the SP CSIreport associated with the SP CSI report trigger index, starting from asecond subframe (or slot). In an example, the second subframe (or slot)may be indicated by the DCI, or the RRC message. In an example, thesecond subframe (or slot) may be a predefined offset from the subframe(or slot) when receiving the DCI. Implementing the example embodimentmay reduce complexity for checking a DCI indicating anactivation/deactivation of a SP CSI report, comparing with thevalidation of activation/deactivation of SPS/type 2 uplink transmission.

In an example, in order to reduce detection error for DCI reception, agNB may transmit a PDCCH with a DCI indicating activation/deactivationof a SP CSI reporting by setting more than one fields in the DCI to oneor more fixed values. In an example, when performing SP CSI reportingrelated actions in response to receiving the DCI, a UE may determine (orvalidate) the PDCCH is valid for activation of a SP CSI reporting, ordeactivation of a SP CSI reporting, based on at least one of: the NDIfield; the HARQ process number; the RV field; the TPC field; the MCSfield; a first downlink assignment index; a second downlink assignmentindex; and/or the RA field. In an example, the UE may determine (orvalidate) the PDCCH is valid for activation of a SP CSI reporting, if atleast one of: the NDI field is set to a first fixed value (e.g., ‘0’ or‘1’ for a 1-bit NDI field); the HARQ process number is set to a secondfixed value (e.g., ‘0000’, or ‘11111’, or a predefined value for a 4-bitHARQ process field); the RV field is set to a third fixed value (e.g.,‘00’, or ‘11’, or a predefined value for a 2-bit RV field). In responseto the PDCCH being valid for activation of a SP CSI report, the UE maytransmit the SP CSI report associated with the SP CSI report triggerindex in multiple subframes. In an example, the UE may determine (orvalidate) the PDCCH is valid for deactivation of a SP CSI reporting, ifat least one of: the NDI field is set to a forth fixed value (e.g., ‘0’or ‘1’, different from the first fixed value); the HARQ process numberis set to a fifth fixed value (e.g., ‘0000’, or ‘11111’, or a predefinedvalue for a 4-bit HARQ process field); the RV field is set to a sixthfixed value (e.g., ‘00’, or ‘11’, or a predefined value for a 2-bit RVfield); the TPC field is set to a seventh fixed value (e.g., ‘00’ or apredefined value, for a 2-bit TPC field); the MCS field is set to aneighth fixed value (e.g., ‘1111’, or a predefined value, for a 4-bit MCSfield); and/or the RA field is set to a ninth fixed value (e.g., set toall ‘1’s). In an example, the fifth value may be same as the secondfixed value. In an example, the sixth value may be same as the thirdfixed value. In response to the PDCCH being valid for deactivation of aSP CSI report, the UE may stop transmitting the SP CSI report associatedwith the SP CSI report trigger index.

In an example, a gNB may change one or more transmission parameters ofan activated SP CSI reporting, to accommodate channel/interferencesituation with dynamic change. In an example, the gNB may indicate anMCS change, or a RA change, or power control command update, by sendinga new DCI. The new DCI may overwrite the corresponding fields of a DCIsent previously for activation of a SP CSI report. In order todifferentiate a DCI indicating parameter change from a DCI foractivation/deactivation, there is a need for a new DCI for indicatingparameters changing of an activated SP CSI reporting. In an example, agNB may transmit a DCI with the NDI field set to a first fixed value(e.g., ‘0’, or ‘1’ for a 1-bit NDI field) indicating one or moretransmission parameter change (or updates), for an activated SP CSIreporting. The gNB may transmit a DCI with the NDI field set to a secondfixed value (e.g., ‘0’ or ‘1’, different from the first fixed value, fora 1-bit NDI field) indicating activation/deactivation of a SP CSIreport.

In an example, when performing a SP CSI reporting related actions, a UEmay determine a DCI is for indicating transmission parameters change (orupdates) for an activated SP CSI reporting, if the NDI field of the DCIis set to the first fixed value. In response to the DCI indicating oneor more parameters change (or updates), the UE may employ the one ormore parameters indicated by the DCI and transmit the activated SP CSIreporting accordingly. In an example, the UE may determine the DCI isfor activation/deactivation of a SP CSI reporting, if the NDI field isset to the second fixed value. In response to the DCI beingactivation/deactivation of a SP CSI reporting, the UE may performvalidation of the PDCCH on which the DCI is transmitted. In an example,the validation is to determine whether the DCI is for activation of a SPCSI reporting, or deactivation of a SP CSI reporting, or the DCI isreceived with a non-matching CRC. In an example, the UE may performvalidation of the PDCCH for activation of a SP CSI reporting, based onat least a first field of the at least second field. In an example, theUE may perform validation of the PDCCH for deactivation of a SP CSIreporting, based on at least a second field of the at least secondfield.

In an example, a UE may perform a validation of a PDCCH for activationof a SP CSI reporting based on at least one of: a HARQ process number; aMCS field; a RA field; a TPC for PUSCH field; a RV field; a CSI requestfield; a first downlink assignment index; a second downlink assignmentindex; a first parameter indicating uplink precoding information andnumber of layers if present; a second parameter indicating antennaports; and/or a third parameter indicating CBG transmission informationif present. In an example, the UE may determine the validation isachieved, if at least one of: the HARQ process number is set to a firstfixed value (e.g., ‘0000’, or ‘1111’, or a predefined value, for a 4-bitHARQ process number); the RV field is set to a second fixed value (e.g.,‘00’, or ‘11’, or a predefined value for a 2-bit RV field); the MCSfield is not a third fixed value (e.g., ‘00000’, or ‘11111’, or apredefined value, for a 5-bit MCS field); the TPC for PUSCH field is nota fourth fixed value (e.g., ‘00’, or ‘11’, or a predefined value, for a2-bit TP field); the RA field is not a fifth fixed value (e.g., set toall ‘1’s); the first parameter is not a first predefined (or fixed)value if present; the second parameter is not a second predefined (orfixed) value; and/or the third parameter is not a third predefined (orfixed) value if present. Otherwise, the UE may determine the validationis not achieved. In the example, the TPC field may indicate the powercontrol command for PUSCH transmission, and/or may not be used forvalidation of PDCCH for activation of SP CSI report. Therefore, the TPCfield may not be set to a fixed value (e.g., the fourth value), whenactivating a SP CSI report by the DCI.

In an example, a UE may perform a validation of a PDCCH for deactivationof a SP CSI reporting based on at least one of: a HARQ process number; aMCS field; a RA field; a TPC for PUSCH field; a RV field; a CSI requestfield; a first downlink assignment index; a second downlink assignmentindex; a first parameter indicating uplink precoding information andnumber of layers if present; a second parameter indicating antennaports; and/or a third parameter indicating CBG transmission informationif present. In an example, the UE may determine the validation isachieved, if at least one of: the HARQ process number is set to a sixthfixed value (e.g., ‘0000’, or ‘1111’, or a predefined value, for a 4-bitHARQ process number); the RV field is set to a seventh fixed value(e.g., ‘00’, or ‘11’, or a predefined value for a 2-bit RV field); theMCS field is set to an eighth fixed value (e.g., ‘00000’, or ‘11111’, ora predefined value, for a 5-bit MCS field); the TPC for PUSCH field isset to a ninth fixed value (e.g., ‘00’, or ‘11’, or a predefined value,for a 2-bit TP field); the RA field is set to a tenth fixed value (e.g.,set to all ‘1’s); the first parameter is a first predefined (or fixed)value if present; the second parameter is a second predefined (or fixed)value; and/or the third parameter is a third predefined (or fixed) valueif present. Otherwise, the UE may determine the validation is notachieved. In an example, the sixth fixed value may be same as the firstfixed value. In an example, the seventh fixed value may be same as thesecond fixed value. In an example, the eighth fixed value may be same asthe third fixed value. In an example, the ninth fixed value may be sameas the fourth fixed value. In an example, the tenth fixed value may besame as the fifth fixed value.

In an example, the UE may determine the DCI is received with anon-matching CRC, if the validation of the PDDCH for activation of a SPCSI reporting is not achieved, and/or the validation of the PDCCH fordeactivation a SP CSI reporting is not achieved. In response to the DCIbeing received with a non-matching CRC, the UE may skip the PDCCH,and/or not perform actions according to the DCI.

In example embodiments, a gNB may transmit a DCI to indicate activationor deactivation of a SP CSI report, by setting one or more values of oneor more DCI fields, without changing the content or format of the CSIrequest field of the DCI or designing a new DCI. These embodiments mayreduce blind decoding attempts of a UE when receiving a PDCCH. The oneor more DCI fields for activation/deactivation of SP CSI report may bedifferent from one more DCI fields for validation ofactivation/deactivation of SPS/type 2 uplink transmission, sinceretransmission and/or power control mechanism may be different for thesetwo cases.

In an example, a DCI indicating activation/deactivation of a SP CSIreport may be different from a DCI for normal dynamic scheduling, or aSPS/type 2 uplink scheduling. In an example, the DCI may not comprise atleast one of: an NDI field; a HARQ process number; the first downlinkassignment index; the second downlink assignment index; and/or a RV,since the at least one of these fields may not be necessary forindication of activation/deactivation of SP CSI report, due to noretransmission required for a SP CSI report on PUSCH. In the example, anew DCI not having at least one of these fields foractivation/deactivation of SP CSI report, may reduce transmissionoverhead, and or blind decoding complexity. A new DCI for activation ordeactivation of a SP CSI report, without these fields may reduce theoverhead of a DCI transmission, carry more CSI parameters, and/orincrease the robustness of the DCI transmission. In an example, a gNBmay transmit to a UE, a DCI for activation/deactivation of SP CSIreporting comprising at least one of: at least one CSI request field; anMCS field; a TPC field; and/or a RA field. The at least one CSI requestfield may comprise at least one of: an activation/deactivationindicator; and/or a SP CSI report trigger index. When theactivation/deactivation indicator in the received DCI indicatesactivation of a SP CSI report, the UE may activate the SP CSI reportassociated with the SP CSI report trigger index. The UE may transmit theSP CSI report indicated by the SP CSI report trigger index in multiplesubframes (or slots), starting from a subframe (or slot). In an example,the subframe (or slot) may be a first available PUSCH subframe (or slot)after the subframe (or slot) when receiving the DCI. In an example, thesubframe (or slot) may be an offset to the subframe (or slot) whenreceiving the DCI. In an example, the offset may be indicated by theDCI, or configured by the RRC message, or a predefined (or fixed) value.The UE may transmit the SP CSI report by employing the TPC command andthe MCS, indicated by the DCI. When the activation/deactivationindicator indicates deactivation of a SP CSI report, the UE maydeactivate the SP CSI report associated with the CSI report triggerindex. The UE may stop transmission of the SP CSI report starting from asubframe (or slot). In an example, the subframe (or slot) may be a firstavailable PUSCH subframe (or slot) after the subframe (or slot) whenreceiving the DCI. In an example, the subframe (or slot) may be anoffset to the subframe (or slot) when receiving the DCI. In an example,the offset may be indicated by the DCI, or configured by the RRCmessage, or a predefined (or fixed) value. In an example, theactivation/deactivation indicator may have one or more bits. When it has1 bit, the activation/deactivation indicator may indicate activation ofa SP CSI report if the bit is ‘1’, or deactivation of a SP CSI report ifthe bit is ‘0’.

In an example, a base station may transmit to a UE, a DCI indicating anactivation/deactivation of a SPS/type 2 GF transmission, anactivation/deactivation of a SP CSI report, or a dynamic scheduling ofuplink transmission or downlink transmission. Example embodimentsprovide methods for dealing with the DCI in an efficient way.

FIG. 35 shows an example embodiment of different actions when receivinga DCI when configured with SP CSI report. In an example, a base station(e.g., gNB in FIG. 35) may transmit to a wireless device (e.g., UE inFIG. 35), at least one message comprising configuration parameters of SPCSI report. The configuration parameters may comprise a first RNTI; andat least one or more SP CSI reporting settings. The at least one messagemay further comprise configuration parameters of SPS/type 2 GFtransmission, wherein, the configuration parameters comprising at leastone of: a second RNTI; and at least one or more SPS/type 2 GF resourceconfiguration; at least one power control parameters. In an example, theat least one message may further comprise at least a third RNTI. The atleast third RNTI may be used for downlink or uplink dynamic scheduling.

In an example, the UE may receive a DCI (e.g., DCI in FIG. 35) via aPDCCH, wherein the DCI may comprise at least one of: an NDI field; andat least a second field. The at least second field may comprise at leastone of: a TPC for PUSCH; a MCS field; a HARQ process number field; a RAfield; a RV field; a CSI request field; a first downlink assignmentindex; a second downlink assignment index; a first parameter indicatinguplink precoding information and number of layers if present; a secondparameter indicating antenna ports; and/or a third parameter indicatingCBG transmission information if present. In an example, the at leastsecond field may comprise at least one CSI request field indicating atleast one of: a SP CSI report trigger index; and/or an indicatorindicating activation/deactivation of a SP CSI report.

In an example, in response to or after receiving the DCI, the UE maydetermine based on CRC bits and/or one or more fields of the DCI,whether the DCI indicates actions (e.g., activation/deactivation) of SPCSI report, or actions (e.g., activation/deactivation/retransmission) ofSPS/type 2 GF transmission, or other actions (e.g., dynamicdownlink/uplink transmission).

In an example, in response to or after receiving the DCI, the UE maydetermine the CRC scramble bits. In an example, the UE may perform SPCSI reporting related actions, if the CRC scramble bits in the receivedDCI are the first RNTI indicated in the at least RRC message. In anexample, the UE may perform SPS/type 2 related actions, if the CRCscramble bits in the received DCI are the second RNTI indicated in theat least RRC message. In an example, the UE may perform required actions(e.g., dynamic transmission), if the CRC scramble bits in the receivedDCI are the at least third RNTI indicated in the at least RRC message.In an example, when performing SPS/type 2 related actions, the UE mayperform a retransmission of the SPS/type 2 uplink data, if the NDI fieldin the received DCI is set to ‘1’. In an example, when performingSPS/type 2 related actions, the UE may perform a validation of thePDCCH, if the NDI field in the received DCI is set to ‘0’. The UE maydetermine the validation of activation/deactivation (or release) of aSPS/type 2 uplink transmission based on at least one of: the TPC field;at least one bit of the MCS field; the HARQ process number field; the RAfield; and/or the RV field.

In an example, a UE may receive, from a base station, at least onemessage comprising configuration parameters of semi-persistent CSI (SPCSI) reporting, wherein, the configuration parameters comprising atleast one of: a first RNTI; and at least one or more SP CSI reportingsettings comprising at least one of: a SP CSI report identifier; and/orone or more SP CSI report parameters. The UE may receive a DCI foractivation/deactivation of a SP CSI report, via a PDCCH comprising atleast one of: a SP CSI report identifier indicating the SP CSI report; afirst field indicating transmission of new data; a second fieldindicating a HARQ process number; a third field indicating a redundancyversion; a fourth field indicating radio resource for transmission of aPUSCH; a fifth field indicating an MCS index.

In an example, the UE may validate the PDCCH for activation/deactivationof the SP CSI report, in response to at least one of: CRC parity bitsfor the DCI being scrambled by the first RNTI; the second field; thethird field; the fourth field; and/or the fifth field.

In an example, the UE may determine the validation for activation of theSP CSI report is achieved, if the second field is set to a firstpredefined value (e.g., all ‘0’s) and the third field is set to a secondpredefined value (e.g., ‘00’). The UE may transmit the SP CSI reportassociated with the SP CSI report identifier, in response to thevalidation being achieved for the DCI indicating the activation of theSP CSI report.

In an example, the UE may determine the validation for deactivation ofthe SP CSI report is achieved, if the second field is set to the firstpredefined value, the third field is set to the second predefined value,the fourth field is set to a third predefined value (e.g., all ‘0’s, all‘1’s, or the like), the fifth field is set to a fourth predefined value(e.g., all ‘1’s). The UE may stop transmission of the SP CSI reportassociated with the SP CSI report identifier, in response to thevalidation being achieved for the DCI indicating the deactivation of theSP CSI report.

In an example, the one or more report parameters may comprise at least:CSI report periodicity; CSI type; one or more RS configurations.

In an example, the first RNTI is different from at least a RNTI forconfigured scheduling (e.g., CS-RNTI); a RNTI for semi-persistentscheduling (e.g., SPS C-RNTI); and/or a RNTI for dynamic scheduling(e.g., C-RNTI).

In an example, the first value is ‘0’, or ‘1’, when the first field is 1bit. In an example, the second value is ‘0000’, or ‘1111’, or apredefined value, when the second field has 4 bits. In an example, thethird value is ‘00’, or ‘11’, or a predefined value, when the thirdfield has 2 bits. In an example, the fourth value is a value with bitsset to all ‘1’s.

In an example, the UE may determine the DCI has been received with anon-matching CRC, if the validation is not achieved. In an example, theUE may skip the DCI in response to the DCI being received with anon-matching CRC.

In a NR system, when configured with multiple beams, a gNB and/or awireless device may perform one or more beam management procedure. Forexample, the wireless device may perform a beam failure recovery request(BFR) procedure, if one or more beam pair links between the gNB and thewireless device fail. The BFR procedure may be referred to as beamfailure detection and recovery procedure, or a beam failure recoveryprocedure.

FIG. 36 shows example of the BFR procedure. A wireless device mayreceive one or more RRC messages comprising BFR parameters 3601. Thewireless device may detect at least one beam failure 3602 according toat least one of BFR parameters. The wireless device may start a firsttimer in response to detecting the at least one beam failure. Thewireless device may select a selected beam 3603 in response to detectingthe at least one beam failure. The wireless device may transmit at leasta first BFR signal 3604 to a gNB in response to the selecting theselected beam. The wireless device may start a response window inresponse to transmitting the at least first BFR signal. In an example,the response window may be a timer with a value configured by the gNB.When the response window is running, the wireless device may monitor aPDCCH in a first coreset 3605. The first coreset may be associated withthe BFR procedure. In an example, the wireless device may monitor thePDCCH in the first coreset in condition of transmitting the at leastfirst BFR signal. The wireless device may receive a first DCI via thePDCCH in the first coreset 3606 when the response window is running. Thewireless device may consider the BFR procedure successfully completed3607 when receiving the first DCI via the PDCCH in the first coresetbefore the response window expires. The wireless device may stop thefirst timer and/or stop the response window in response to the BFRprocedure successfully being completed.

In an example, when the response window expires, the wireless device mayset a BFR transmission counter to a value (e.g., one). In an example, inresponse to the response window expiring, the wireless device may,before the first timer expires, perform one or more actions comprisingat least one of: a BFR signal transmission; starting the responsewindow; monitoring the PDCCH; incrementing the BFR transmission counter(e.g., by one) in response to the response window expiring. In anexample, the wireless device may repeat the one or more actions untilthe BFR procedure successfully is completed, or the first timer expires,or the BFR transmission counter indicates a value equal to or greaterthan a configured transmission number.

In an example, when the first timer expires, and the wireless devicedoes not receive the DCI, the wireless device may declare (or indicate)the BFR procedure failure 3608. In an example, when the transmissionnumber of the BFR signals is greater than the configured transmissionnumber, the wireless device may declare (or indicate) the BFR procedurefailure.

In an example, a wireless device may fail in a first random accessprocedure for a beam failure recovery. The first random access proceduremay be a contention-free random access procedure as shown in FIG. 16Bgenerally and/or as shown in FIG. 36 specifically. The wireless devicemay fail in the first random access procedure due to at least one of: anexpiry of a beam failure recovery timer; preamble transmissions reachinga configured number.

In an example, existing beam failure recovery procedures may comprisetwo independent or separate random access procedures, a firstcontention-free random access procedure (e.g., as shown in FIG. 16B) fora beam failure recovery and a second contention-based random accessprocedure (e.g., as shown in FIG. 16A) for the beam failure recovery. Awireless device, implementing the existing beam failure recoveryprocedures, may initiate the second random access procedure when thewireless device fails in the first random access procedure. Since thefirst and the second random access procedures are independent, thewireless device may, by initiating the second random access procedure,reset a value of a preamble transmission counter to an initial value(e.g., 1), reset one or more power parameters to initial power values,and/or start transmission of a preamble with the preamble transmissioncounter setting to the initial value. In an example, resetting thepreamble transmission counter to the initial value may increase a numberof preamble transmissions in the second random access procedure.Existing beam failure recovery procedures may be inefficient, take along time, or increase battery power consumption, e.g. the random accessprocedure may increase a duration of beam failure recovery procedure andincrease power consumption for the wireless device. Example embodimentsprovide processes for the wireless device and the base station toenhance beam failure recovery procedures. Example embodiment may enhanceefficiency of beam failure recovery procedure when the wireless devicedoes not receive a response from a gNB after a beam failure recoverytimer expires or a preamble transmission number reaches a configurednumber. Example embodiments may reduce a duration of beam failurerecovery procedure and may reduce battery power consumption.

FIG. 37 shows an example embodiment of an enhanced beam failure recovery(BFR) procedure. In an example, a base station (e.g., gNB in FIG. 37)may transmit to a wireless device (e.g., UE in FIG. 37), one or more RRCmessages comprising one or more configuration parameters of a BFRprocedure. The one or more configuration parameters of the BFR proceduremay comprise a first threshold; a second threshold; and/or a firstcontrol resource set (e.g., coreset) associated with the BFR procedure.In an example, the first coreset may comprise multiple RBs in thefrequency domain, at least a symbol in the time domain.

In an example, the one or more configuration parameters of the BFRprocedure may indicate a first set of RSs for beam failure detection;and/or one or more PRACH resources associated with a second set of RSs(beams) for candidate beam selection. In an example, the one or morePRACH resources may comprise at least one of: one or more preambles;and/or one or more time/frequency resources. In an example, each RS ofthe second set of RSs may be associated with a preamble, a timerresource and/or a frequency resource of one of the one or more PRACHresources. In an example, the one or more RRC messages may furthercomprise configuration parameters of one or more contention-based PRACHresources.

In an example, the one or more configuration parameters of the BFRprocedure may indicate one or more PUCCH or scheduling request (SR)resources associated with a third set of RSs (beams). In an example, theone or more PUCCH or SR resource may comprise at least one of: timeallocation; frequency allocation; cyclic shift; orthogonal cover code;and/or a spatial setting. In an example, each RS of the third set of RSsmay be associated with each of the one or more PUCCH/SR resources.

In an example, the first set of RSs may be one or more first CSI-RSs orone or more first SSBs. In an example, the second set of RSs may be oneor more second CSI-RSs or one or more second SSBs. In an example, thethird set of RSs may be one or more third CSI-RSs or one or more thirdSSBs. In an example, a BFR signal may be a PRACH preamble transmittedvia a time/frequency resource of a PRACH resource. The PRACH resourcemay be selected from the one or more PRACH resources associated with thesecond set of RSs (beams) for candidate beam selection, or from the oneor more contention-based PRACH resources. In an example, a BFR signalmay be a PUCCH/SR transmitted on a PUCCH/SR resource.

In an example, the one or more configuration parameters of the BFRprocedure may further comprise a first timer value (e.g., one of 10 ms,20 ms, 40 ms, 60 ms, 80 ms, 100 ms, 150 ms, 200 ms) of beam failurerecovery timer (e.g., beamFailureRecoveryTimer), a preamble transmissionnumber (e.g., preambleTransMax with a value of one of 3, 4, 5, 6, 7, 8,10, 20, 50, 100, and 200), a second timer value (e.g., one of 1 slot, 2slots, 4 slots, 8 slots, 10 slots, 20 slots, 40 slots and 80 slots) abeam failure recovery response window (e.g., bfr-reponse-window), and/ora beam failure instance number (e.g., beamFadureinstanceMaxCount with avalue of one of 1, 2, 3, 4, 5, 6, 8 and 10).

In an example, the UE may detect one or more beam failure instances whena quality (e.g., RSRP or SINR) of at least one of the first set of RSsis lower than the first threshold. when the one or more beam failureinstances reach the beam failure instance number (e.g.,beamFadureinstanceMaxCount), the UE may start the beam failure recoverytimer (e.g., BFR timer as shown in FIG. 37) with the first timer valueand initiate a random access procedure (e.g., RA as shown in FIG. 37)for the beam failure recovery. The random access procedure may startfrom a contention-free random access procedure. Initiating the randomaccess procedure may comprise setting a preamble transmission counter(e.g., preamble Tx counter as shown in FIG. 37) to an initial value(e.g., 1).

In an example, the UE may select at least one beam associated with atleast one of the second set of RSs based on the second threshold. In anexample, the UE may select the at least one beam when the measuredquality (e.g., RSRP or SINR) of a RS associated the at least one beam isgreater than the second threshold. The UE may select a BFR signal (e.g.,a 1^(st) preamble as shown in FIG. 37) based on the at least one beam.The UE may transmit the BFR signal to a gNB (e.g, at slot/subframe n₁).In an example, the BFR signal may be a PRACH preamble associated withthe at least one beam. the association between the BFR signal and thePRACH preamble may be indicated in the one or more configurationparameters of the BFR procedure. In an example, the BFR signal may be aPUCCH/SR signal associated with the at least one beam.

In an example, in response to transmitting the BFR signal, the UE maystart monitoring a first PDCCH for receiving a DCI, in the firstcoreset, after a time period since transmitting the BFR signal (e.g., inslot/subframe n₁+k as shown in FIG. 37). The DCI may comprise a responseto the BFR signal. The time period may be a fixed period (e.g., 4slots), or a configured value by an RRC message. The UE may start thebeam failure recovery response window with the second timer value afterthe time period since transmitting the BFR signal. The wireless devicemay monitor the first PDCCH in the first coreset during the beam failurerecovery response window.

In an example, the UE may receive the DCI via the first PDCCH in thefirst coreset during the beam failure recovery response window. Thewireless device may consider the BFR procedure (e.g., successfully)completed in response to receiving the DCI via the first PDCCH in thefirst coreset.

In an example, the UE may not receive the DCI via the first PDCCH in thefirst coreset during the beam failure recovery response window. Inresponse to an expiry of the beam failure recovery window (e.g., atslot/subframe n₁+k+l), the UE may increment the preamble transmissioncounter (e.g., by one) and transmit a second BFR signal (e.g., 2^(nd)preamble as shown in FIG. 37). In response to not receiving the DCIduring the beam failure recovery response window, the UE may repeat oneor more actions comprising at least one of: transmitting a preamble;starting the beam failure recovery response window; monitoring the firstPDCCH; and/or incrementing the preamble transmission counter.

In an example, the beam failure recovery timer may expire during thebeam failure recovery procedure. In response to an expiry of the beamfailure recovery timer, the UE may store (keep or not reset) thepreamble transmission counter. The UE may store (keep or not reset) thepreamble transmission counter if the preamble transmission counterindicates a value equal to or less than the preamble transmission number(e.g., preambleTransMax). By storing (or keeping or not resetting) thepreamble transmission counter, the UE may continue the random accessprocedure for the beam failure recovery. The UE may continue the randomaccess procedure by using the one or more contention-based PRACHresources.

In an example, in response to the expiry of the beam failure recoverytimer, the UE may store the preamble transmission counter. The UE mayselect a new beam and/or a third preamble. In response to the preambletransmission counter being less than the preamble transmission number(e.g., preambleTransMax), the UE may transmit the third preamble (e.g,3rd preamble as shown in FIG. 37). Example embodiments improve existingBFR procedures by continuing a BFR procedure after a contention-freerandom access procedure fails, specially not resetting the preambletransmission counter. By the example embodiments, a first part of therandom access procedure before a contention-free random access procedurefails and a second part of the random access procedure after thecontention-free random access procedure fails, may become a singleprocedure, resulting in improved efficiency and batter power reductionfor the UE when performing the beam failure recovery. Exampleembodiments may enhance efficiency of beam failure recovery procedurewhen the wireless device does not receive a response from a gNB after abeam failure recovery timer expires. Example embodiments may reduce aduration of beam failure recovery procedure and may reduce battery powerconsumption.

FIG. 38 shows an example embodiment of an enhanced beam failure recovery(BFR) procedure. In an example, a base station (e.g., gNB in FIG. 38)may transmit to a wireless device (e.g., UE in FIG. 38), one or more RRCmessages comprising one or more configuration parameters of a BFRprocedure. The one or more RRC messages may further comprise a firstPRACH resource set (e.g., 1^(st) PRACH resource set in FIG. 38) and asecond PRACH resource set (e.g., 2^(nd) PRACH resource set in FIG. 38).The one or more configuration parameters of the BFR procedure maycomprise a first threshold; a second threshold; and/or a first controlresource set (e.g., coreset) associated with the BFR procedure. In anexample, the first coreset may comprise multiple RBs in the frequencydomain, at least a symbol in the time domain.

In an example, the one or more configuration parameters of the BFRprocedure may indicate a first set of RSs for beam failure detection;and/or one or more PRACH resources associated with a second set of RSs(beams) for candidate beam selection. In an example, the one or morePRACH resources may comprise at least one of: one or more preambles;and/or one or more time/frequency resources. In an example, the one ormore PRACH resources may be the first PRACH resource set. In an example,each RS of the second set of RSs may be associated with a preamble, atimer resource and/or a frequency resource of one of the one or morePRACH resources. In an example, the one or more RRC messages may furthercomprise configuration parameters of one or more contention-based PRACHresources. The one or more contention-based PRACH resources may be thesecond PRACH resource set.

In an example, a BFR signal may be a PRACH preamble transmitted via atime/frequency resource of a PRACH resource. The PRACH resource may beselected from the one or more PRACH resources associated with the secondset of RSs (beams) for candidate beam selection, or from the one or morecontention-based PRACH resources. The preamble may be selected from thefirst PRACH resource set or the second PRACH resource set.

In an example, the one or more configuration parameters of the BFRprocedure may further comprise a first timer value of beam failurerecovery timer (e.g., beamFailureRecoveryTimer), a preamble transmissionnumber (e.g., preambleTransMax), a second timer value of a beam failurerecovery response window (e.g, bfr-reponse-window), and/or a beamfailure instance number (e.g., beamFailureInstanceMaxCount).

In an example, the UE may detect one or more beam failure instances whena quality (e.g., RSRP or SINR) of at least one of the first set of RSsis lower than the first threshold. when the one or more beam failureinstances reach the beam failure instance number (e.g.,beamFailureInstanceMaxCount), the UE may start the beam failure recoverytimer (e.g., BFR timer as shown in FIG. 38) with the first timer valueand initiate a random access procedure (e.g., RA as shown in FIG. 38)for the beam failure recovery. The random access procedure may startfrom a contention-free random access procedure. Initiating the randomaccess procedure may comprise setting a preamble transmission counter(e.g., preamble Tx counter as shown in FIG. 38) to an initial value(e.g., 1).

In an example, the UE may select at least one beam associated with atleast one of the second set of RSs based on the second threshold. In anexample, the UE may select the at least one beam when the measuredquality (e.g., RSRP or SINR) of a RS associated the at least one beam isgreater than the second threshold. The UE may select a first preamble(e.g., a 1^(st) preamble as shown in FIG. 38) from the first PRACHresource set, based on the at least one beam. The UE may transmit thefirst preamble to a gNB (e.g, at slot/subframe n₁). In an example, thefirst preamble may be a PRACH preamble associated with the at least onebeam. the association between the first preamble and the PRACH preamblemay be indicated in the one or more configuration parameters of the BFRprocedure.

In an example, in response to transmitting the first preamble, the UEmay start monitoring a first PDCCH for receiving a DCI, in the firstcoreset, after a time period since transmitting the first preamble(e.g., in slot/subframe n₁+k as shown in FIG. 38). The DCI may comprisea response to the first preamble. The time period may be a fixed period(e.g., 4 slots), or a configured value by an RRC message. The UE maystart the beam failure recovery response window with the second timervalue after the time period since transmitting the first preamble. Thewireless device may monitor the first PDCCH in the first coreset duringthe beam failure recovery response window.

In an example, the UE may receive the DCI via the first PDCCH in thefirst coreset during the beam failure recovery response window. Thewireless device may consider the BFR procedure successfully completed inresponse to receiving the DCI via the first PDCCH in the first coreset.

In an example, the UE may not receive the DCI via the first PDCCH in thefirst coreset during the beam failure recovery response window. Inresponse to an expiry of the beam failure recovery window (e.g., atslot/subframe n₁+k+l), the UE may increment the preamble transmissioncounter (e.g., by one). The UE may select a second preamble (e.g.,2^(nd) preamble in FIG. 38) from the first PRACH resource set. The UEmay transmit the second preamble in response to selecting the secondpreamble. The selecting the second preamble is based on the firstthreshold, same as selecting the first preamble. In response to notreceiving the DCI during the beam failure recovery response window, theUE may repeat one or more actions comprising at least one of:transmitting a preamble; starting the beam failure recovery responsewindow; monitoring the first PDCCH; and/or incrementing the preambletransmission counter.

In an example, the beam failure recovery timer may expire during thebeam failure recovery procedure. In response to an expiry of the beamfailure recovery timer, the UE may store (keep or not reset) thepreamble transmission counter. By storing (or keeping or not resetting)the preamble transmission counter, the UE may continue the random accessprocedure for the beam failure recovery. The UE may continue the randomaccess procedure by using the second PRACH resource set. The secondPRACH resource set may be a contention-based preamble and RACH resourceset.

In an example, in response to the expiry of the beam failure recoverytimer, the UE may store the preamble transmission counter. The UE mayselect a third preamble (e.g, 3rd preamble as shown in FIG. 38) from thesecond PRACH resource set. In response to the preamble transmissioncounter being less than the preamble transmission number (e.g.,preambleTransMax), and selecting the third preamble, the UE may transmitthe third preamble. Example embodiments improve existing BFR proceduresby continuing a BFR procedure after a contention-free random accessprocedure fails, specially not resetting the preamble transmissioncounter. By the example embodiments, the random access procedure, beforeand after a contention-free random access procedure fails (e.g., due toan expiry of the beam failure recovery timer), may become a singleprocedure, resulting in improved efficiency and batter power reductionfor the UE when performing the beam failure recovery. Exampleembodiments may enhance efficiency of beam failure recovery procedurewhen the wireless device does not receive a response from a gNB after abeam failure recovery timer expires. Example embodiments may reduce aduration of beam failure recovery procedure and may reduce battery powerconsumption.

In an example, the wireless device may trigger a BFR procedure when anumber of beam failure instances (e.g. contiguous) are detected. A beamfailure instance may occur when quality of a beam pair link is lowerthan a configured threshold. For example, a beam failure instance mayoccur when the RSRP value or SINR value of a beam pair link is lowerthan a first threshold, or the BLER (block error rate) of the beam pairlink is higher than a second threshold. Triggering a BFR procedure bysporadic beam failure instances may increase power consumption of thewireless device. Example embodiment provides methods and systems fortriggering a BFR procedure.

FIG. 39 shows an example embodiment of an enhanced beam failure recoveryprocedure. In an example, a base station (e.g., gNB in FIG. 39) maytransmit to a wireless device (e.g., UE in FIG. 39), one or more RRCmessages comprising one or more configuration parameters of a BFRprocedure. The one or more configuration parameters of the BFR proceduremay comprise a first threshold; a second threshold; and/or a firstcontrol resource set (e.g., coreset) associated with the BFR procedure.The one or more configuration parameters of the BFR procedure mayindicate a first set of RSs for beam failure detection; and/or one ormore PRACH resources associated with a second set of RSs (beams) forcandidate beam selection. In an example, the one or more PRACH resourcesmay comprise at least one of: one or more preambles; and/or one or moretime/frequency resources. In an example, each RS of the second set ofRSs may be associated with a preamble, a timer resource and/or afrequency resource of one of the one or more PRACH resources. In anexample, the one or more RRC messages may further comprise configurationparameters of one or more contention-based PRACH resources.

In an example, the one or more configuration parameters of the BFRprocedure may further comprise a first timer value of beam failurerecovery timer (e.g., beamFailureRecoveryTimer), a preamble transmissionnumber (e.g., preambleTransMax), a second timer value of a beam failurerecovery response window (e.g, bfr-reponse-window), a beam failureinstance number (e.g., beamFailureinstanceMaxCount), a third timer valueof a beam failure detection timer (e.g., beamFailureDetectionTimer);and/or a periodicity of beam failure instance indication.

In an example, a physical layer of the wireless device (e.g., Physicallayer of the UE in FIG. 39) may measure the first set of RSs. Thephysical layer may indicate one or more beam failure instance (e.g.,beam failure instance indication as shown in FIG. 39) or one or morebeam non-failure instance periodically to a higher layer (e.g., MAClayer or layer 3, as shown in FIG. 39) of the wireless device, based onthe first threshold. In an example, the physical layer may indicate abeam failure instance when the measured quality (e.g., RSRP or SINR) ofat least one of the first set of RSs is lower than the first threshold.In an example, the physical layer may indicate a beam failure instancewhen the measured quality (e.g., a hypothetic BLER) of at least one ofthe first set of RSs is higher than the first threshold. In an example,the physical layer may indicate a beam non-failure instance when themeasured quality (e.g., RSRP or SINR) of at least one of the first setof RSs is equal to or higher than the first threshold. In an example,the physical layer may indicate a beam non-failure instance when themeasured quality (e.g., a hypothetic BLER) of at least one of the firstset of RSs is lower than the first threshold. In an example, theperiodicity of the indication may be a value configured by the gNB or besame as the periodicity of transmission of the first set of RSs.

In an example, a MAC entity of the wireless device may set a beamfailure instance counter to a value (e.g., one) in response to receivinga first beam failure indication from the physical layer. In an example,when receiving a contiguous second beam failure indication, the MACentity may increment the beam failure instance counter (e.g., by one).In an example, when receiving a third beam non-failure indication, theMAC entity may reset the beam failure instance counter (e.g., to zero).

In an example, when receiving a first beam failure indication from thephysical layer, the MAC entity may start the beam failure detectiontimer (e.g., beamFailureDetectionTimer) with the third timer value. Whenreceiving a second beam non-failure indication from the physical layer,the MAC entity may restart the beam failure detection timer. When thebeam failure detection timer expires, and the beam failure instancecounter indicates a value smaller than the beam failure instance number,the MAC entity may not trigger the BFR procedure. In an example, the MACentity may reset the beam failure instance counter (e.g., 0), when thebeam failure detection timer expires, and/or the beam failure instancecounter indicates a value smaller than the beam failure instance number.In an example, the MAC entity may reset the beam failure detection timerto the third timer value, when the beam failure detection timer expires,and/or the beam failure instance counter indicates a value smaller thanthe beam failure instance number.

In an example, as shown in FIG. 39, when the beam failure instancecounter indicates a value equal to or greater than the beam failureinstance number, or beam failure indications (e.g., contiguous) receivedby the MAC entity reaches the beam failure instance number, the MACentity of the wireless device may trigger a BFR procedure. The wirelessdevice may initiate the BFR procedure (as shown in FIG. 39).

In an example, in response to the beam failure instance counterindicates a value equal to or greater than the beam failure instancenumber, the MAC entity of the wireless device may indicate to thephysical layer to stop beam failure instance indication, when triggeringthe BFR procedure. Indicating to the physical layer of the UE to stopbeam failure instance indication may save batter power of the UE whenthe BFR procedure is ongoing.

FIG. 40 shows an example embodiment of an enhanced beam failure recoveryprocedure. In an example, a base station (e.g., gNB in FIG. 40) maytransmit to a wireless device (e.g., UE in FIG. 40), one or more RRCmessages comprising one or more configuration parameters of a BFRprocedure. The one or more configuration parameters of the BFR proceduremay comprise a first threshold; a second threshold; and/or a firstcontrol resource set (e.g., coreset) associated with the BFR procedure.The one or more configuration parameters of the BFR procedure mayindicate a first set of RSs for beam failure detection; and/or one ormore PRACH resources associated with a second set of RSs (beams) forcandidate beam selection. In an example, the one or more PRACH resourcesmay comprise at least one of: one or more preambles; and/or one or moretime/frequency resources. In an example, each RS of the second set ofRSs may be associated with a preamble, a timer resource and/or afrequency resource of one of the one or more PRACH resources. In anexample, the one or more RRC messages may further comprise configurationparameters of one or more contention-based PRACH resources.

In an example, the one or more configuration parameters of the BFRprocedure may further comprise a first timer value of beam failurerecovery timer (e.g., beamFailureRecoveryTimer), a preamble transmissionnumber (e.g., preambleTransMax), a second timer value of a beam failurerecovery response window (e.g, bfr-reponse-window), a beam failureinstance number (e.g., beamFailureinstanceMaxCount), a third timer valueof a beam failure detection timer (e.g., beamFailureDetectionTimer);and/or a periodicity of beam failure instance indication.

In an example, a physical layer of the wireless device (e.g., Physicallayer of the UE in FIG. 40) may measure the first set of RSs. Thephysical layer may indicate one or more beam failure instance (e.g.,beam failure instance indication as shown in FIG. 40) or one or morebeam non-failure instance periodically to a higher layer (e.g., MAClayer or layer 3, as shown in FIG. 40) of the wireless device, based onthe first threshold. In an example, the physical layer may indicate abeam failure instance when the measured quality (e.g., RSRP or SINR) ofat least one of the first set of RSs is lower than the first threshold.In an example, the physical layer may indicate a beam failure instancewhen the measured quality (e.g., a hypothetic BLER) of at least one ofthe first set of RSs is higher than the first threshold. In an example,the physical layer may indicate a beam non-failure instance when themeasured quality (e.g., RSRP or SINR) of at least one of the first setof RSs is equal to or higher than the first threshold. In an example,the physical layer may indicate a beam non-failure instance when themeasured quality (e.g., a hypothetic BLER) of at least one of the firstset of RSs is lower than the first threshold. In an example, theperiodicity of the indication may be a value configured by the gNB or besame as the periodicity of transmission of the first set of RSs.

In an example, a MAC entity of the wireless device may set a beamfailure instance counter to a value (e.g., one) in response to receivinga first beam failure indication from the physical layer. In an example,when receiving a contiguous second beam failure indication, the MACentity may increment the beam failure instance counter (e.g., by one).In an example, when receiving a third beam non-failure indication, theMAC entity may reset the beam failure instance counter (e.g., to zero).

In an example, when receiving a first beam failure indication from thephysical layer, the MAC entity may start the beam failure detectiontimer (e.g., beamFailureDetectionTimer) with the third timer value. Whenreceiving a second beam non-failure indication from the physical layer,the MAC entity may restart the beam failure detection timer. When thebeam failure detection timer expires, and the beam failure instancecounter indicates a value smaller than the beam failure instance number,the MAC entity may not trigger the BFR procedure. In an example, the MACentity may reset the beam failure instance counter (e.g., 0), when thebeam failure detection timer expires, and/or the beam failure instancecounter indicates a value smaller than the beam failure instance number.In an example, the MAC entity may reset the beam failure detectiontimer, when the beam failure detection timer expires, and/or the beamfailure instance counter indicates a value smaller than the beam failureinstance number.

In an example, as shown in FIG. 40, when the beam failure instancecounter indicates a value equal to or greater than the beam failureinstance number, or beam failure indications (e.g., contiguous) receivedby the MAC entity reaches the beam failure instance number, the MACentity of the wireless device may trigger a BFR procedure. The wirelessdevice may initiate the BFR procedure (as shown in FIG. 40).

In an example, in response to the beam failure instance counterindicating a value equal to or greater than the beam failure instancenumber, when the triggered BFR procedure is ongoing, the MAC entity ofthe wireless device may reset the beam failure instance counter (e.g.,to zero), reset the beam failure detection timer, and/or ignore theperiodic beam failure instance indication. Example embodiments mayimprove power consumption, time delay, or uplink interference whenperforming a beam failure recovery procedure.

FIG. 41 shows an example embodiment of an enhanced beam failure recoveryprocedure. In an example, a base station (e.g., gNB in FIG. 41) maytransmit to a wireless device (e.g., UE in FIG. 41), one or more RRCmessages comprising one or more configuration parameters of a BFRprocedure. The one or more configuration parameters of the BFR proceduremay comprise a first threshold; a second threshold; and/or a firstcontrol resource set (e.g., coreset) associated with the BFR procedure.In an example, the first coreset may comprise multiple RBs in thefrequency domain, at least a symbol in the time domain.

In an example, the one or more configuration parameters of the BFRprocedure may indicate a first set of RSs for beam failure detection;and/or one or more PRACH resources associated with a second set of RSs(beams) for candidate beam selection. In an example, the one or morePRACH resources may comprise at least one of: one or more preambles;and/or one or more time/frequency resources. In an example, each RS ofthe second set of RSs may be associated with a preamble, a timerresource and/or a frequency resource of one of the one or more PRACHresources. In an example, the one or more RRC messages may furthercomprise configuration parameters of one or more contention-based PRACHresources.

In an example, the one or more configuration parameters of the BFRprocedure may indicate one or more PUCCH or scheduling request (SR)resources associated with a third set of RSs (beams). In an example, theone or more PUCCH or SR resource may comprise at least one of: timeallocation; frequency allocation; cyclic shift; orthogonal cover code;and/or a spatial setting. In an example, each RS of the third set of RSsmay be associated with each of the one or more PUCCH/SR resources.

In an example, the first set of RSs may be one or more first CSI-RSs orone or more first SSBs. In an example, the second set of RSs may be oneor more second CSI-RSs or one or more second SSBs. In an example, thethird set of RSs may be one or more third CSI-RSs or one or more thirdSSBs. In an example, a BFR signal may be a PRACH preamble transmittedvia a time/frequency resource of a PRACH resource. The PRACH resourcemay be selected from the one or more PRACH resources associated with thesecond set of RSs (beams) for candidate beam selection, or from the oneor more contention-based PRACH resources. In an example, a BFR signalmay be a PUCCH/SR transmitted on a PUCCH/SR resource.

In an example, the one or more configuration parameters of the BFRprocedure may further comprise a first timer value of beam failurerecovery timer (e.g., beamFailureRecoveryTimer), a preamble transmissionnumber (e.g., preambleTransMax), a second timer value of a beam failurerecovery response window (e.g, bfr-reponse-window), and/or a beamfailure instance number (e.g., beamFailureInstanceMaxCount).

In an example, the UE may detect one or more beam failure instances whena quality (e.g., RSRP or SINR) of at least one of the first set of RSsis lower than the first threshold. when the one or more beam failureinstances reach the beam failure instance number (e.g.,beamFailureInstanceMaxCount), the UE may start the beam failure recoverytimer (e.g., BFR timer as shown in FIG. 41) with the first timer valueand initiate a random access procedure (e.g., RA as shown in FIG. 41)for the beam failure recovery. The random access procedure may startfrom a contention-free random access procedure. Initiating the randomaccess procedure may comprise setting a preamble transmission counter(e.g., preamble Tx counter as shown in FIG. 41) to an initial value(e.g., 1).

In an example, the UE may perform a contention-free random accessprocedure for the BFR, when the beam failure recovery timer is running.In an example, the UE may select at least one beam associated with atleast one of the second set of RSs based on the second threshold. In anexample, the UE may select the at least one beam when the measuredquality (e.g., RSRP or SINR) of a RS associated the at least one beam isgreater than the second threshold. The UE may select a BFR signal (e.g.,a n^(th) preamble as shown in FIG. 41) based on the at least one beam.The UE may transmit the BFR signal to a gNB.

In an example, in response to transmitting the BFR signal, the UE maystart monitoring a first PDCCH for receiving a DCI, in the firstcoreset. The UE may start the beam failure recovery response window withthe second timer value after the time period since transmitting the BFRsignal. The wireless device may monitor the first PDCCH in the firstcoreset during the beam failure recovery response window.

In an example, the UE may not receive the DCI via the first PDCCH in thefirst coreset during the beam failure recovery response window. Inresponse to an expiry of the beam failure recovery window, the UE mayincrement the preamble transmission counter (e.g., by one) and transmita second BFR signal (e.g., (n+1)^(th) preamble as shown in FIG. 41). Inresponse to not receiving the DCI during the beam failure recoveryresponse window, the UE may repeat one or more actions comprising atleast one of: transmitting a preamble; starting the beam failurerecovery response window; monitoring the first PDCCH; and/orincrementing the preamble transmission counter.

In an example, the beam failure recovery timer may expire during thebeam failure recovery procedure. In response to an expiry of the beamfailure recovery timer, the UE may store (keep or not reset) thepreamble transmission counter. By storing (or keeping or not resetting)the preamble transmission counter, the UE may continue the random accessprocedure for the beam failure recovery. The UE may continue the randomaccess procedure by using the one or more contention-based PRACHresources.

In an example, in response to the expiry of the beam failure recoverytimer, the UE may store the preamble transmission counter. The UE mayselect a new beam and/or a third preamble (e.g., (n+2)^(th) preamble asshown in FIG. 41). In response to the preamble transmission counterbeing less than the preamble transmission number (e.g.,preambleTransMax), the UE may transmit the third preamble. In responseto transmitting the third preamble, the UE may monitor a second PDCCHfor a response to the third preamble during a response window. The UEmay not receive the response to the third preamble during the responsewindow. In response to not receiving the response, the UE may incrementthe preamble transmission counter and/or select a fourth preamble (e.g.,(n+3)^(th) preamble as shown in FIG. 41). The UE may transmit the fourthpreamble in response to the preamble transmission counter being lessthan the preamble transmission number (e.g., preambleTransMax). Exampleembodiments improve existing BFR procedures by continuing a BFRprocedure after a contention-free random access procedure fails,specially not resetting the preamble transmission counter, e.g., untilinitiating a new random access procedure. By the example embodiments,the random access procedure, before and after a contention-free randomaccess procedure fails (e.g., due to an expiry of the beam failurerecovery timer), may become a single procedure, resulting in improvedefficiency and batter power reduction for the UE when performing thebeam failure recovery. Example embodiments may enhance efficiency ofbeam failure recovery procedure when the wireless device does notreceive a response from a gNB after a beam failure recovery timerexpires. Example embodiments may reduce a duration of beam failurerecovery procedure and may reduce battery power consumption.

FIG. 42 shows an example embodiment of an enhanced beam failure recoveryprocedure. In an example, a base station (e.g., gNB in FIG. 42) maytransmit to a wireless device (e.g., UE in FIG. 42), one or more RRCmessages comprising one or more configuration parameters of a BFRprocedure. The one or more configuration parameters of the BFR proceduremay comprise a first threshold; a second threshold; and/or a firstcontrol resource set (e.g., coreset) associated with the BFR procedure.In an example, the first coreset may comprise multiple RBs in thefrequency domain, at least a symbol in the time domain.

In an example, the one or more configuration parameters of the BFRprocedure may indicate a first set of RSs for beam failure detection;and/or one or more PRACH resources associated with a second set of RSs(beams) for candidate beam selection. In an example, the one or morePRACH resources may comprise at least one of: one or more preambles;and/or one or more time/frequency resources. In an example, each RS ofthe second set of RSs may be associated with a preamble, a timerresource and/or a frequency resource of one of the one or more PRACHresources. In an example, the one or more RRC messages may furthercomprise configuration parameters of one or more contention-based PRACHresources.

In an example, the one or more configuration parameters of the BFRprocedure may indicate one or more PUCCH or scheduling request (SR)resources associated with a third set of RSs (beams). In an example, theone or more PUCCH or SR resource may comprise at least one of: timeallocation; frequency allocation; cyclic shift; orthogonal cover code;and/or a spatial setting. In an example, each RS of the third set of RSsmay be associated with each of the one or more PUCCH/SR resources.

In an example, the first set of RSs may be one or more first CSI-RSs orone or more first SSBs. In an example, the second set of RSs may be oneor more second CSI-RSs or one or more second SSBs. In an example, thethird set of RSs may be one or more third CSI-RSs or one or more thirdSSBs. In an example, a BFR signal may be a PRACH preamble transmittedvia a time/frequency resource of a PRACH resource. The PRACH resourcemay be selected from the one or more PRACH resources associated with thesecond set of RSs (beams) for candidate beam selection, or from the oneor more contention-based PRACH resources. In an example, a BFR signalmay be a PUCCH/SR transmitted on a PUCCH/SR resource.

In an example, the one or more configuration parameters of the BFRprocedure may further comprise a first timer value of beam failurerecovery timer (e.g., beamFailureRecoveryTimer), a preamble transmissionnumber (e.g., preambleTransMax), a second timer value of a beam failurerecovery response window (e.g, bfr-reponse-window), and/or a beamfailure instance number (e.g., beamFailureInstanceMaxCount).

In an example, the UE may detect one or more beam failure instances whena quality (e.g., RSRP or SINR) of at least one of the first set of RSsis lower than the first threshold. when the one or more beam failureinstances reach the beam failure instance number (e.g.,beamFailureInstanceMaxCount), the UE may start the beam failure recoverytimer (e.g., BFR timer as shown in FIG. 42) with the first timer valueand initiate a random access procedure (e.g., RA as shown in FIG. 42)for the beam failure recovery. The random access procedure may startfrom a contention-free random access procedure. Initiating the randomaccess procedure may comprise setting a preamble transmission counter(e.g., preamble Tx counter as shown in FIG. 42) to an initial value(e.g., 1).

In an example, the UE may perform a contention-free random accessprocedure for the BFR, when the beam failure recovery timer is running.In an example, the UE may select at least one beam associated with atleast one of the second set of RSs based on the second threshold. In anexample, the UE may select the at least one beam when the measuredquality (e.g., RSRP or SINR) of a RS associated the at least one beam isgreater than the second threshold. The UE may select a BFR signal (e.g.,a n^(th) preamble as shown in FIG. 42) based on the at least one beam.The UE may transmit the BFR signal to a gNB.

In an example, in response to transmitting the BFR signal, the UE maystart monitoring a first PDCCH for receiving a DCI, in the firstcoreset. The UE may start the beam failure recovery response window withthe second timer value after the time period since transmitting the BFRsignal. The wireless device may monitor the first PDCCH in the firstcoreset during the beam failure recovery response window.

In an example, the UE may not receive the DCI via the first PDCCH in thefirst coreset during the beam failure recovery response window. Inresponse to an expiry of the beam failure recovery window, the UE mayincrement the preamble transmission counter (e.g., by one) and transmita second BFR signal (e.g., (n+1)^(th) preamble as shown in FIG. 42). Inresponse to not receiving the DCI during the beam failure recoveryresponse window, the UE may repeat one or more actions comprising atleast one of: transmitting a preamble; starting the beam failurerecovery response window; monitoring the first PDCCH; and/orincrementing the preamble transmission counter.

In an example, the beam failure recovery timer may expire during thebeam failure recovery procedure. In response to an expiry of the beamfailure recovery timer, the UE may store (keep or not reset) thepreamble transmission counter. By storing (or keeping or not resetting)the preamble transmission counter, the UE may continue the random accessprocedure for the beam failure recovery. The UE may continue the randomaccess procedure by using the one or more contention-based PRACHresources.

In an example, in response to the expiry of the beam failure recoverytimer, the UE may store the preamble transmission counter. The UE mayselect a new beam and/or a third preamble (e.g., (n+2)^(th) preamble asshown in FIG. 42). In response to the preamble transmission counterbeing less than the preamble transmission number (e.g.,preambleTransMax), the UE may transmit the third preamble. In responseto transmitting the third preamble, the UE may monitor a second PDCCHfor a response to the third preamble during a response window. The UEmay not receive the response to the third preamble during the responsewindow.

In an example, in response to not receiving the response during theresponse window, the UE may increment the preamble transmission counter.The preamble transmission counter may indicate a value equal to thepreamble transmission number (e.g., preambleTransMax) plus 1. Inresponse to the preamble transmission counter indicating the value equalto the preamble transmission number (e.g., preambleTransMax) plus 1, theUE may complete the BFR procedure. The example embodiments improveexisting BFR procedures by continuing a BFR procedure after acontention-free random access procedure fails, specially not resettingthe preamble transmission counter, e.g., until initiating a new randomaccess procedure. By the example embodiments, the random accessprocedure, before and after a contention-free random access procedurefails (e.g., due to an expiry of the beam failure recovery timer), maybecome a single procedure, resulting in improved efficiency and batterpower reduction for the UE when performing the beam failure recovery.Example embodiments may enhance efficiency of beam failure recoveryprocedure when the wireless device does not receive a response from agNB after a beam failure recovery timer expires. Example embodiments mayreduce a duration of beam failure recovery procedure and may reducebattery power consumption.

In an example, a first control resource (e.g., coreset) is associatedwith a BFR procedure. a wireless device may monitor a first PDCCH in thefirst coreset in response to transmitting a BFR signal for the BFRprocedure. The wireless device may not monitor the first PDCCH in thefirst coreset in response to not transmitting the BFR signal. In anexample, the gNB may not transmit a PDCCH in the first coreset if thegNB does not receive the BFR signal. The gNB may transmit a PDCCH in asecond coreset if the gNB does not receive the BFR signal. The secondcoreset, in which the wireless monitor a PDCCH before the BFR procedureis triggered, is different from the first coreset.

In existing technologies of beam failure recovery procedures, after awireless device declares (or indicates) a failure of a beam failurerecovery procedure, a wireless device may keep monitoring a first PDCCH,for a response to preamble transmission in a first control resource set(e.g., a coreset) and may miss detect a second PDCCH in a second controlresource set (e.g., on which the base station and the wireless devicemaintain a communication link). In an example, miss-detecting the secondPDCCH may result in the connection link lost, or result in transmissionlatency. Example embodiments may improve connection continuity whenperforming beam failure recovery procedure.

FIG. 43 shows an example embodiment of an enhanced beam failure recoveryprocedure. The wireless device may start a beam failure recovery timer(e.g., beamFailureRecoveryTimer) when detecting a number of beamfailures (e.g., contiguous). The wireless device may transmit a firstBFR signal at n₁ ^(th) slot, after selecting at least one beam. Thewireless device may start monitoring a first PDCCH in a first coreset at(n₁+k)^(th) slot. k may be a predefined value (e.g., 4). The wirelessdevice may start a beam failure recovery response window (e.g.,bfr-response-window) at (n₁+k)^(th) slot in response to transmitting thefirst BFR signal. In an example, when the wireless device receives a DCIon the first PDCCH at least in the first coreset before thebfr-response-window expires, the wireless device may consider the BFRprocedure successfully completed. In an example, in response to the BFRprocedure being successfully completed, the wireless device may stop thebeamFailureRecoveryTimer and/or the bfr-response-window.

In an example, when the bfr-response-window expires at (n₁+k+l)^(th)slot, the wireless device may set the BFR transmission counter to avalue (e.g., one), transmit a second BFR signal, and monitor the firstPDCCH during the bfr-response-window is running. In an example, thewireless device may repeat at least one of: transmitting the BFR signal;starting the bfr-response-window; monitoring the first PDCCH;incrementing the BFR transmission counter (e.g., by one) in response tothe bfr-response-window expiring, until the beamFailureRecoveryTimerexpires, or the BFR transmission counter indicates a value equal to orgreater than a configured preamble transmission number.

As shown in FIG. 43, when the beamFailureRecoveryTimer expires, and theBFR transmission counter indicates a value smaller than configuredpreamble transmission number, the wireless device may perform at leastone of: indicating a first type of information to higher layers (e.g.,MAC or RRC layer); cancelling the transmission of BFR signal; stoppingmonitoring the first PDCCH in the first coreset; monitoring the secondPDCCH on the second coreset; starting detecting one or more beam failureinstance; and starting selecting one new beam. In an example, thewireless device may not reset the BFR transmission counter. In anexample, the wireless device may reset the BFR transmission counter(e.g., zero). In an example, the first type of information may compriseat least one of: the BFR timer being expiring; beam failure recoveryprocedure failure; and/or out of synchronization.

In an example, the wireless device may retransmit the BFR signals, ifthe BFR transmission counter indicate a first value smaller than theconfigured preamble transmission number, until the BFR transmissioncounter indicates a second value equal to or great than the configurednumber.

In an example, in response to the BFR transmission counter indicating avalue equal to or greater than the configured preamble transmissionnumber, the wireless device may perform at least one of: indicating asecond type of information to higher layers of the wireless device;stopping the beamFailureRecoveryTimer; stopping the BFR signaltransmission; resetting the BFR transmission counter (e.g., zero);stopping monitoring the first PDCCH in the first coreset; startingmonitoring a second PDCCH in a second coreset; starting detecting one ormore beam failure instance; and starting selecting one new beam. In anexample, the second type of information may comprise at least one of: aBFR transmission number being equal to greater than the configuredpreamble transmission number; beam failure recovery procedure failure;and/or out of synchronization.

FIG. 44 shows an example embodiment of an enhanced beam failure recoveryprocedure. In the example, the beamFailureRecoveryTimer may beconfigured with a first timer value (e.g., an infinity value), which maybe running even when the BFR transmission counter indicates a valueequal to or greater than the configured number of BFR transmission. Inthe example, the wireless device may, in response to the BFRtransmission counter indicating a value equal to or greater than theconfigured number of BFR transmission, perform at least one of:indicating a second type of information to higher layers of the wirelessdevice; stopping the beamFailureRecoveryTimer; stopping the BFR signaltransmission; resetting the BFR transmission counter (e.g., to zero);stopping monitoring the first PDCCH in the first coreset; startingmonitoring the second PDCCH in the second coreset; starting detectingone or more beam failure instance; and/or starting selecting one newbeam. Stopping the beamFailureRecoveryTimer, when the BFR transmissioncounter indicates a value equal to or greater than the configured numberof BFR transmission, may avoid starting from a contention-based randomaccess procedure for a next beam failure recovery procedure.

By the embodiments, a wireless device may perform one or more actionswhen the BFR transmission number reaches the configured number oftransmissions of BFR signals and the wireless device does not receive aresponse from a gNB. The one or more actions may lead to reducing thepower consumption of PDCCH monitoring, for example, by stopping monitorthe coreset dedicated for the BFR procedure and/or switching to monitora coreset on which the wireless device monitors before the BFR procedurestarts. The one or more actions may lead to reducing the powerconsumption of transmitting the BFR signal, for example, by stoppingtransmitting the BFR signal. The one or more actions may lead to improvesuccess rate of the BFR procedure, for example, by starting beam failuredetection and/or new beam selection.

In an example, the wireless device may start a beam failure recoverytimer (e.g., beamFailureRecoveryTimer) when detecting a number of beamfailures (e.g., contiguous). When the beamFailureRecoveryTimer isrunning, the wireless device may not select a candidate beam satisfyingthe selection requirement, for example, due to no RS from the second setof RSs having a receiving quality (e.g., RSRP or SINR) than a configuredthreshold.

In an example, when no candidate beam indication received from thephysical layer during the beamFailureRecoveryTimer is running, the MACentity may indicate a third type of information to higher layers upon anexpiry of the beamFailureRecoveryTimer. In an example, the third type ofinformation may comprise at least one of: no candidate beam beingselected; beam failure recovery procedure failure; and/or out ofsynchronization.

In an example, higher layers (e.g., RRC) of a wireless device mayinstruct the MAC entity or the physical layer of the wireless device toperform one or more actions based on received the one or moreinformation. In an example, the one or more information may comprise atleast one of: a first information indicating an expiry ofbeamFailureRecoveryTimer with no response received on a PDCCH; a secondinformation indicating a configured transmission number of BFR signalreached; a third information indicating an expiry ofbeamFailureRecoveryTimer with no new beam identified by the physicallayer. In an example, different information may indicate differentcauses of beam failure recovery procedure failure. In an example, thehigher layers may indicate (or declare) a radio link failure with theone or more information. In an example, the wireless device may storethe one or more information in one or more radio link failure report. Inan example, the wireless device may start an RRC connectionre-establishment procedure with one or more RRC messages comprising theone or more radio link failure reports. In an example, the wirelessdevice and/or the gNB may take different actions according to thedifferent information comprised in the one or more radio link failurereports. For example, when the one or more information received at thegNB in a radio link failure report is an expiry of thebeamfailureRecoveryTimer with no new beam identified by the wirelessdevice, the gNB may transmit one or more RRC message comprisingparameters indicating one or more RSs configuration based on the one ormore information in the radio link failure report, after the RRCconnection re-establishment procedure successfully finished. In anexample, the one or more RSs may be used for new candidate beamselection.

In an example, a wireless device may receive from a base station, atleast one message comprising configuration parameters indicating atleast one of: one or more preambles; a first value of a first timerindicating a response window; a second value of a BFR timer; a firstnumber of transmissions of one of the one or more preambles; a firstcoreset; and/or a second coreset. In an example, the wireless device maystart the BFR timer associated with the second value, in response todetecting at least a first beam failure. In an example, the wirelessdevice may reset a transmission counter to a value (e.g., zero). In anexample, the wireless device may transmit at least a preamble in a firstslot. In an example, the wireless device may start the first timerassociated with the first value after the first slot, in response totransmitting the at least preamble. The wireless device may monitor afirst PDCCH in the first coreset at least during a portion of a timerperiod when the first timer is running. In an example, the wirelessdevice may increment the transmission counter (e.g., by one), inresponse to the first timer expiring. In an example, when thetransmission counter indicates a value equal to or greater than thefirst number, the wireless device may perform at least one of: resettingthe transmission counter (e.g., to zero); starting to monitor a secondPDCCH in the second coreset; stopping the BFR timer.

In an example, the first coreset may comprise a first control resourceset comprising a first number of OFDM symbols and a first set ofresource blocks. In an example, the second coreset may comprise a secondnumber of OFDM symbols and a second set of resource blocks.

In an example, the at least first beam failure occurs when the qualityof the beam is lower than a configured threshold.

In an example, the wireless device may consider the BFR proceduresuccessfully completed when receiving a DCI via the first PDCCH when thefirst timer is running. In an example, the wireless device may stop theBFR timer and/or the first timer, in response to the BFR procedure beingsuccessfully completed.

In an example, the wireless may repeat at least one of: transmitting thepreamble; starting the first timer; monitoring the first PDCCH;incrementing the transmission counter (e.g., by one) in response to thefirst timer expiring, until the BFR timer expires, or the transmissioncounter indicates a value equal to or great than the first number, orthe BFR procedure is successfully completed.

In an example, when the transmission counter indicates a value equal toor greater than the first number, the wireless device may perform atleast one of: cancelling the preamble transmission; stopping monitoringthe first PDCCH on the first coreset; indicating a first type ofinformation to at least a higher layer (e.g., MAC or RRC); starting todetect one or more beam failure instance; starting to select at leastone reference signal; initiating a random access procedure. In anexample, the first type of information may comprise at least one of:random access problem; beam failure recovery timer expiring; reachingthe configured transmission number; beam failure recovery procedurefailure; no beam being selected; out of synchronization.

In an example, when there is a big amount of transmission blocks (TBs)to be transmitted to a UE and/or the UE is in a changing channelcondition, a UE may transmit frequent CSI reports to a base station forfacilitating downlink channel scheduling. In an example, aperiodic CSIreport may not be efficient in this case, where the UE may transmit theaperiodic CSI report in one shot. The aperiodic CSI report may betriggered by a DCI. Request for multiple and/or frequent CSI reports maybe achieved by transmitting multiple DCIs, which may increase DCItransmission and reduce the capacity of PDCCH. In an example, periodicCSI report may not work efficient or convenient in this case. Theperiodic CSI report may be configured or reconfigured in an RRC message.An RRC message for the periodic CSI report may not be efficient toenable or disable the frequent CSI reports. In an example, a basestation may transmit a DCI via downlink control channel, indicating SPCSI activation/deactivation. The DCI transmission may not be efficient,or cause extra power consumption for a wireless device to detect theDCI. A MAC CE based SP CSI activation/deactivation mechanism may beefficient and/or improve power consumption of the wireless device.Example embodiments of MAC CE based SP CSI activation/deactivation mayimprove efficiency of downlink transmission, batter power consumptionfor SP CSI report.

In an example, a wireless device may receive from a base station, atleast an RRC message comprising configuration parameters of one or moreSP CSI report on PUCCH, wherein, the configuration parameters compriseat least one of: one reference signal (RS) resource setting; and/or oneor more SP CSI reporting settings. The RS resource setting may comprisea set of RS resources, each RS resource associated with a RS resourceconfiguration identifier and radio resource configuration (e.g., numberof ports; time and frequency resource allocation; frequency density;etc.). In an example, the RS may be a CSI-RS, and/or a SS block. In anexample, a SP CSI report setting may comprise a set of SP CSI reportparameters comprising at least one of: a SP CSI report identifier;and/or one or more parameters for SP CSI reporting, wherein, the one ormore parameters may comprise at least one of: a CSI type (e.g., Type Ior Type II); a report quantity indicator (e.g., indicating a CSI-relatedquantity to report, or a L1-RSRP related quantity to report, etc.); areport configuration type (e.g., indicating the time domain behavior ofthe report—either aperiodic, semi-persistent, or periodic); a valueindicating frequency granularity for CSI report; parameters indicatingperiodicity; slot offset of CSI report; and/or a PUCCH resource. A UEmay transmit a SP CSI report on the PUCCH resource, associated with theSP CSI report identifier.

In an example, the at least RRC message may further comprise linkparameters of one or more SP CSI reports on PUCCH. In an example, linkparameters of a SP CSI report may comprise at least one of: a SP CSIreport trigger index; one RS resource configuration identifier; and/orone SP CSI report identifier. The RS resource configuration identifiermay indicate one RS resource associated with the SP CSI report. The SPCSI report identifier may indicate SP CSI report parameters associatedwith the SP CSI report.

In an example, a wireless device may receive a MAC message comprising atleast one of: a MAC subheader; and/or a MAC CE. The MAC CE may compriseat least one of: at least a SP CSI report trigger index; at least anactivation/deactivation field; and/or reserve bits. The at least SP CSIreport trigger index may indicate triggering one of the one or more SPCSI reports. The at least activation/deactivation field may indicateactivation or deactivation of the triggered SP CSI report associatedwith the at least SP CSI report trigger index.

FIG. 45A shows an example embodiment of a MAC CE ofactivation/deactivation of SP CSI report. In an example, as shown inFIG. 45A, the MAC CE of activation/deactivation of SP CSI report maycomprise: at least an activation/deactivation field (e.g., Act/Deact asshown in FIG. 45A); and at least a SP CSI report trigger index (e.g., SPCSI report trigger index as shown in FIG. 45A); and/or a R bit. The atleast activation/deactivation field may be 1 bit. The at least SP CSIreport trigger index may be a value of 6 bits. In an example, the atleast activation/deactivation field may have 2 bits (e.g., where, “00”may indicate activation, “11” may indicate deactivation, or vice versa),and the at least SP CSI report trigger index may have 6 bits. In anexample, the at least activation/deactivation field may indicateactivation of a SP CSI report on PUCCH if the bit is “0”, ordeactivation of a SP CSI report if the bit is “1”. In an example, the atleast activation/deactivation field may indicate deactivation of a SPCSI report on PUCCH if the bit is “0”, or activation of a SP CSI reportif the bit is “1”. In an example, the at least SP report trigger indexmay have one or more bits (e.g., 2; 3; 4; or 5), based on theconfiguration.

FIG. 45B shows an example embodiment of a MAC subheader identifying theMAC CE of activation/deactivation of SP CSI report. In an example, theMAC subheader may comprise a 6-bit LCID field and a 2-bit R field. Avalue of the LCID field for SP CSI report activation/deactivation MAC CEmay be different from other LCIDs for other MAC CE or logical channels.For example, the LCID with a value of “110111” may indicate SP CSIreport activation/deactivation MAC CE. In an example, the MAC subheadermay not have a length field, since the MAC CE for SP CSI reportactivation/deactivation may have a fixed length (e.g., 8 bits as shownin FIG. 45A).

In an example, in response to receiving the MAC CE, a wireless devicemay determine whether the MAC CE indicate activation or deactivation ofa SP CSI report. If the at least activation/deactivation field in theMAC CE indicates activation of a SP CSI report, the wireless device maydetermine the RS resource indicated by the RS resource configurationidentifier associated with the SP CSI report trigger index. The wirelessdevice may measure CSI parameters (e.g., CQI; PMI; RI; CRI; and/orL1-RSRP) indicated by the SP CSI report identifier associated with theSP CSI report trigger index. The wireless device may transmit on aPUCCH, SP CSI reports based on the measured CSI parameters, wherein, thePUCCH is associated with the SP CSI report identifier.

In an example, if the at least activation/deactivation field in the MACCE indicates deactivation of a SP CSI report on PUCCH, the wirelessdevice may stop transmission of the SP CSI report associated with the SPCSI report trigger index indicated in the MAC CE.

By the method of the embodiment, a gNB may transmit a MAC message to aUE indicating activation or deactivation of a SP CSI report on PUCCH.With the example embodiment of MAC CE and MAC subheader, a gNB mayefficiently activate or deactivate a SP CSI report on PUCCH for awireless device. With the example embodiment of MAC CE and MACsubheader, a wireless device may reduce power consumption for SP CSIreport on PUCCH.

In an example, a gNB may transmit one or more RRC message comprisingparameters of a plurality of cells comprising a primary cell and atleast one secondary cell, wherein, the parameters of a secondary cellmay comprise at least one of: a SCell index; and/or radio resourceconfiguration of the secondary cell. In an example, the SCell index maybe an integer greater than 0 and less than 8, if carrier aggregationoperation with at most 7 SCells is supported. In an example, the SCellindex may be an integer greater than 0 and less than 32, if carrieraggregation operation with at most 31 SCells is supported.

FIG. 46A shows an example embodiment of MAC CE ofactivation/deactivation of SP CSI report of multiple cells. In anexample, with at most 7 SCells configured, a UE may receive a MACmessage comprising at least one of: a MAC CE; and/or a MAC subheader,wherein, the MAC CE may have variable size, comprising at least: a firstoctet; and one or more second octet. In an example, C_(i) in the firstoctet (e.g., Oct 1 in FIG. 46A) may indicate the presence of anactivation/deactivation field of a SP CSI report for a secondary cellwith a SCell index i (0<i<8). A C_(i) field set to “0” may indicate thatactivation/deactivation of a SP CSI report for a secondary cell with aSCell index i (0<i<8) is not present. A C_(i) field set to “1” mayindicate that activation/deactivation of a SP CSI report for a secondarycell with a SCell index i (0<i<8) is present. C₀ may be a reserved bit.A second octet (e.g., Oct 2 in FIG. 46A) may indicateactivation/deactivation of a SP CSI report for a PCell. The second octetmay comprise at least one of: a first bit indicatingactivation/deactivation of a SP CSI report; a second field indicating aSP CSI report trigger index; and/or one or more reserve bits. The firstbit set to “1” may activate a SP CSI report associated with the SP CSIreport trigger index. The first bit set to “0” may deactivate a SP CSIreport associated with the SP CSI report trigger index. In an example,there may be a third octet (e.g., Oct 3 in FIG. 46A) corresponding to aPSCell, if the PSCell is configured, wherein, the third octet maycomprise at least one of: a first bit indicating activation/deactivationof a SP CSI report; a second field indicating a SP CSI report triggerindex; and/or one or more reserve bits.

In an example, if C₁ is set to “1”, a fourth octet may indicateactivation/deactivation of a SP CSI report for the SCell with a SCellindex 1. In an example, if C₁ is set to “0”, the activation/deactivationof SP CSI report for the SCell with a SCell index 1 may be not present.If C₂ is set to “1”, a fifth octet (if C₁ is set to “1”, otherwise thefourth octet) may indicate activation/deactivation of a SP CSI reportfor the SCell with a SCell index 2, etc.

In an example, the MAC CE may indicate activation/deactivation of SP CSIreports for multiple SCells. The length of the MAC CE may be variabledepending on the number of SCells triggered with SP CSI reports. In anexample, a MAC subheader may indicate SP CSI activation/deactivation MACCE for multiple SCells, wherein the MAC subheader may comprise at leastone of: a LCID field; a length field; a format field indicating the sizeof the length field; and/or one or more reserved bits.

FIG. 46B shows an example embodiment of a MAC subheader identifying theSP CSI activation/deactivation MAC CE. A LCID field in the MACsubheader, for a MAC CE of activation/deactivation of SP CSI reports formultiple SCells, may be different from other LCIDs of other MAC CEand/or logic channels. The length field in the MAC subheader mayindicate the length of the MAC CE of activation/deactivation of SP CSIreports for multiple SCells.

FIG. 47 shows an example embodiment of a MAC CE ofactivation/deactivation of SP CSI report of multiple cells. In anexample, with at most 31 SCells configured, a UE may receive a MACmessage comprising at least one of: a MAC CE; and/or a MAC subheader.The MAC CE may have variable size. The MAC CE may comprise at least: afirst four octets (e.g., Oct 1, Oct 2, Oct 3 and Oct 4 in FIG. 47); andone or more fifth octet (e.g., Oct 5 in FIG. 47). The first four octetsmay indicate a presence/absence of an activation/deactivation field of aSP CSI report for a secondary cell with a SCell index i (0<i<32). AC_(i) field set to “0” may indicate that activation/deactivation of a SPCSI report for a secondary cell with a SCell index i (0<i<32) is notpresent. A C_(i) field set to “1” may indicate thatactivation/deactivation of a SP CSI report for a secondary cell with aSCell index i (0<i<32) is present. C₀ may be a reserved bit. The fifthoctet (e.g., Oct 5 in FIG. 47) may indicate activation/deactivation of aSP CSI report for a PCell. The fifth octet may comprise at least one of:a first bit indicating activation/deactivation of a SP CSI report; asecond field indicating a SP CSI report trigger index; and/or one ormore reserve bits. The first bit set to “1” may activate a SP CSI reportassociated with the SP CSI report trigger index. The first bit set to“0” may deactivate a SP CSI report associated with the SP CSI reporttrigger index. In an example, there may be a sixth octet correspondingto a PSCell, if the PSCell is configured.

In an example, if C₁ is set to “1”, a seventh octet may indicateactivation/deactivation of a SP CSI report for the SCell with a SCellindex 1. In an example, if C₁ is set to “0”, the activation/deactivationof SP CSI report for the SCell with a SCell index 1 may be not present.In an example, if C₂ is set to “1”, an eighth octet (if C₁ is set to“1”, otherwise the seventh octet) may indicate activation/deactivationof a SP CSI report for the SCell with a SCell index 2, etc.

In an example, a gNB may decouple the link between a SP CSI report and aCSI-RS (or SS blocks) configuration, to make it flexible of activating aSP CSI report. For example, a gNB may transmit a MAC message comprisingparameters indicating activation/deactivation of a SP CSI report and aRS resource configuration.

In an example, a wireless device may receive from a base station, atleast an RRC message comprising configuration parameters of one or moreSP CSI report on PUCCH, wherein, the configuration parameters compriseat least one of: one reference signal (RS) resource setting; and/or oneor more SP CSI reporting settings. The RS resource setting may comprisea set of RS resources, each RS resource associated with radio resourceconfiguration (e.g., number of ports; time and frequency resourceallocation; frequency density; etc.) of a RS, each RS associated with aRS resource configuration identifier. In an example, the RS may be aCSI-RS, and/or a SS block. In an example, one SP CSI report setting maycomprise a set of SP CSI report parameters comprising at least one of: aSP CSI report identifier; and/or one or more parameters for SP CSIreporting, wherein the one or more parameters may comprise at least oneof: a CSI type (e.g., Type I or Type II); a report quantity indicator(e.g., indicating a CSI-related quantity to report, or a L1-RSRP relatedquantity to report, etc.); a report configuration type (e.g., indicatingthe time domain behavior of the report—either aperiodic,semi-persistent, or periodic); a value indicating frequency granularityfor CSI report; parameters indicating periodicity; slot offset of CSIreport; and/or a PUCCH resource.

FIG. 48A shows an example embodiment of MAC CE ofactivation/deactivation of SP CSI report and RS resource configuration.In an example, a gNB may transmit a MAC message comprising at least oneof: a MAC CE; and/or a MAC subheader, wherein the MAC CE may compriseparameters indicating at least one of: activation/deactivation of a SPCSI report on PUCCH; a RS resource configuration. In an example, a firstoctet (e.g., Oct 0 as shown in FIG. 48A) in the MAC CE may indicateactivation or deactivation of a SP CSI report associated with the SP CSIreport ID. The first octet may comprise at least one of: a firstactivation/deactivation field indicating activation or deactivation of aSP CSI report; a SP CSI report ID indicate one of the one or more SP CSIreports to be triggered; and/or one or more reserved bits. A secondoctet (e.g., Oct 1 in FIG. 48A) in the MAC CE may indicate a RS resourceconfiguration associated with the RS resource configuration ID. Thesecond octet may comprise at least: a RS resource configuration IDindicating one of the one or more RS resources for the SP CSI report.

In an example, a second octet in the MAC CE may indicate activation ordeactivation of a RS resource associated with the RS resourceconfiguration ID (e.g., if the RS resource is a SP RS). The second octetmay comprise at least one of: a first activation/deactivation fieldindicating activation or deactivation of a RS resource; a RS resourceconfiguration ID indicating one of the one or more RS resources.

In response to receiving the MAC CE, a wireless device may determine oneor more RS for a SP CSI report based on the second octet in the MAC CE.The wireless device may determine activation or deactivation of a SP CSIreport based on the first octet in the MAC CE. If theactivation/deactivation field in the first octet indicates activation ofa SP CSI report, the wireless device may measure CSI parametersassociated with the SP CSI report ID, on the one or more RS. Thewireless device may transmit one or more SP CSI repots based on themeasurement, on a PUCCH associated with the SP CSI report ID. If theactivation/deactivation field in the first octet of the MAC CE indicatesdeactivation of a SP CSI report, the wireless device may stoptransmission of the SP CSI report associated with the SP CSI report ID.

FIG. 48B shows an example embodiment of the MAC subheader identifyingthe MAC CE. In an example, a MAC subheader may comprise at least one of:a LCID field; a R field, wherein, the LCID field may be a 6-bit valuededicated to indicating activation/deactivation of a SP CSI report andRS resource configuration. The R field may be two reserved bits. The MACsubheader may not have a length field, since the MAC CE for SP CSIreport activation/deactivation and RS resource configuration may have afixed length (e.g., 16 bits as shown in FIG. 48A). The LCID for the MACCE of SP CSI report activation/deactivation and RS resourceconfiguration may have a value different to other LCIDs for other MAC CEor logical channels.

In an example, a gNB may transmit one or more RRC message comprisingparameters of a plurality of cells comprising a primary cell and atleast one secondary cell, wherein, the parameters of a secondary cellmay comprise at least one of: a SCell index; and/or radio resourceconfiguration of the secondary cell. In an example, the SCell index maybe an integer greater than 0 and less than 8, if carrier aggregationoperation with at most 7 SCells is supported. In an example, the SCellindex may be an integer greater than 0 and less than 32, if carrieraggregation operation with at most 31 SCells is supported.

FIG. 49A shows an example embodiment of MAC CE ofactivation/deactivation of SP CSI report and RS resource configurationon multiple cells. In an example, with at most 7 SCells configured, a UEmay receive a MAC message comprising at least one of: a MAC CE; and/or aMAC subheader, wherein, the MAC CE may have variable size, comprising atleast: a first octet (e.g., Oct 1 in FIG. 49A); a second octet (e.g.,Oct 2 in FIG. 49A); a third octet (e.g., Oct 3 in FIG. 49A); and/or oneor more fourth octet (e.g., Oct 4/5/m/m+1 in FIG. 49A). In an example,C_(i) in the first octet may indicate the presence of anactivation/deactivation field and a RS resource configuration field of aSP CSI report for a secondary cell with a SCell index i (0<i<8). A C_(i)field set to “0” may indicate that activation/deactivation and a RSresource configuration of a SP CSI report for a secondary cell with aSCell index i (0<i<8) is not present. A C_(i) field set to “1” mayindicate that activation/deactivation and a RS resource configuration ofa SP CSI report for a secondary cell with a SCell index i (0<i<8) ispresent. C₀ may be a reserved bit. The second octet (Oct 2) may indicateactivation/deactivation of a SP CSI report for a PCell. The second octetmay comprise at least one of: a first bit indicatingactivation/deactivation of a SP CSI report; a second field indicating aSP CSI report trigger index; and/or one or more reserve bits. The firstbit set to “1” may activate a SP CSI report associated with the SP CSIreport trigger index. The first bit set to “0” may deactivate a SP CSIreport associated with the SP CSI report trigger index. The third octetmay comprise parameters indicating at least a RS configuration ID, whichmay be used for measurement for the SP CSI report. In an example, theremay be a fourth and a fifth octets corresponding to a PSCell, if thePSCell is configured.

In an example, if C₁ is set to “1”, a sixth octet and a seventh octetmay indicate activation/deactivation of a SP CSI report, and a RSresource configuration associated with the SP CSI report for the SCellwith a SCell index 1. In an example, if C₁ is set to “0”, theactivation/deactivation of SP CSI report and the RS resourceconfiguration for the SCell with a SCell index 1 may be not present. IfC₂ is set to “1”, an eighth and ninth octets (if C₁ is set to “1”,otherwise the sixth and seventh octets) may indicateactivation/deactivation of a SP CSI report and a RS resourceconfiguration associated with the SP CSI report for the SCell with aSCell index 2, etc.

FIG. 49B shows an example embodiment of the MAC subheader identifyingthe MAC CE. In an example, the MAC CE may indicateactivation/deactivation of SP CSI reports and RS resource configurationfor multiple SCells. The length of the MAC CE may be variable dependingon the number of SCells triggered with SP CSI reports. In an example,the MAC subheader may indicate MAC CE of SP CSI activation/deactivationand RS resource configuration for multiple SCells, wherein the MACsubheader may comprise at least one of: a LCID field; a length field; aformat field indicating the size of the length field; and/or one or morereserved bits. The LCID field in the MAC subheader, for a MAC CE ofactivation/deactivation and RS resource configuration of SP CSI reportsand RS resource configuration for multiple SCells, may be different fromother LCIDs of other MAC CE and/or logic channels. The length field inthe MAC subheader may indicate the length of the MAC CE ofactivation/deactivation and RS resource configuration of SP CSI reportsfor multiple SCells.

FIG. 50 shows an example embodiment of a MAC CE ofactivation/deactivation of SP CSI report and RS resource configurationon multiple cells. In an example, when more than 8 SCells areconfigured, first 4 octets of the MAC CE (e.g., Oct 1, Oct 2, Oct 3 andOct 4 in FIG. 50) indicate presence/absence of anactivation/deactivation fields of a SP CSI report and CSI-RSconfiguration for a secondary cell with a SCell index i (0<i<32). Anoctet pair may indicate activation or deactivation of a SP CSI report(by a first octet) and a RS configuration associated with the SP CSIreport (by a second octet), for a SCell.

In an example, a wireless device may receive from a base station, atleast one message comprising configuration parameters of one or moresemi-persistent CSI (SP CSI) report, wherein, the configurationparameters indicate at least: one or more CSI trigger index, eachassociated with at least one of: one or more CSI RSs associated withradio resource configuration; one SP CSI reporting setting associatedwith a SP CSI report identifier; and one or more parameters for SP CSIreporting. The wireless device may receive a Media Access Control (MAC)commend comprising at least one of: a SP CSI report trigger fieldindicating one of the one or more SP CSI report; and/or an indicatorfield indicating activation or deactivation of the one of the one ormore SP CSI report. The wireless device may transmit the SP CSI report,if the indicator field associated with the SP CSI report indicatingactivation of the SP CSI report, in response to receiving the MACcommand. In an example, the wireless device may stop transmission of theSP CSI report, if the indicator field associated with the SP CSI reportindicating deactivation of the SP CSI report, in response to receivingthe MAC command.

According to various embodiments, a device such as, for example, awireless device, off-network wireless device, a base station, a corenetwork device, and/or the like, may comprise one or more processors andmemory. The memory may store instructions that, when executed by the oneor more processors, cause the device to perform a series of actions.Embodiments of example actions are illustrated in the accompanyingfigures and specification. Features from various embodiments may becombined to create yet further embodiments.

FIG. 51 is a flow diagram of an aspect of an embodiment of the presentdisclosure. At 5110, a wireless device may receive a downlink controlinformation from a base station. The downlink control information maycomprise a power control command of an uplink shared channel. Thedownlink control information may comprise a channel state information(CSI) request field. The downlink control information may comprise ahybrid automatic repeat request process number. The downlink controlinformation may comprise a redundancy version. At 5120, a validation ofthe downlink control information for an activation of a semi-persistentCSI reporting may be performed based on a radio network temporaryidentifier of the semi-persistent CSI reporting. A validation of thedownlink control information for an activation of a semi-persistent CSIreporting may be performed based on the hybrid automatic repeat requestprocess number being set to a first value. A validation of the downlinkcontrol information for an activation of a semi-persistent CSI reportingmay be performed based on the redundancy version being set to a secondvalue. At 5130, the semi-persistent CSI reporting indicated by the CSIrequest field may be activated in response to the validation beingachieved. At 5140, a semi-persistent CSI report may be transmitted,based on the activated semi-persistent CSI reporting, via the uplinkshared channel with a transmission power determined based on the powercontrol command.

According to an example embodiment, the wireless device may determinethe validation is achieved in response to cyclic redundancy check paritybits of the downlink control information being scrambled with the radionetwork temporary identifier of the semi-persistent CSI reporting. Thewireless device may determine the validation is achieved in response tothe hybrid automatic repeat request process number being set to thefirst value. The wireless device may determine the validation isachieved in response to the redundancy version being set to the secondvalue. According to an example embodiment, the semi-persistent CSIreport may comprise a channel quality indicator (CQI). Thesemi-persistent CSI report may comprise a precoding matrix indicator(PMI). The semi-persistent CSI report may comprise a channel stateinformation reference signal resource indicator (CRI). Thesemi-persistent CSI report may comprise a layer indicator (LI). Thesemi-persistent CSI report may comprise a rank indicator (RI). Thesemi-persistent CSI report may comprise a layer 1 reference signalreceived power (L1-RSRP). According to an example embodiment, thewireless device may transmit the semi-persistent CSI report with areport periodicity of the activated semi-persistent CSI reporting.According to an example embodiment, the first value may be a predefinedvalue comprising a bit string with bits set to “0”. According to anexample embodiment, the second value may be a predefined valuecomprising a bit string with bits set to “0”.

According to an example embodiment, the downlink control information maycomprise a new data indicator field. According to an example embodiment,the wireless device may validate the downlink control informationregardless of a value of the new data indicator field and a value of thepower control command. According to an example embodiment, the downlinkcontrol information may be skipped by not applying the downlink controlinformation in response to the validation not being achieved. Accordingto an example embodiment, the validation may not be achieved in responseto cyclic redundancy check parity bits of the downlink controlinformation not being scrambled with the radio network temporaryidentifier of the semi-persistent CSI reporting. The semi-persistent CSIreport may comprise the hybrid automatic repeat request process numbernot being set to the first value. The semi-persistent CSI report maycomprise the redundancy version not being set to the second value.

According to an example embodiment, the downlink control information maycomprise a value indicating a modulation and coding scheme. The downlinkcontrol information may comprise a parameter of resource blockassignment on the uplink shared channel. According to an exampleembodiment, the wireless device may determine the validation is achievedin response to the value indicating the modulation and coding scheme notbeing set to a third value. The wireless device may determine thevalidation is achieved in response to the parameter of the resourceblock assignment not being set to a fourth value. According to anexample embodiment, the wireless device may transmit the semi-persistentCSI report via one or more resource blocks of the uplink shared channel.The one or more resource blocks may be indicated by the parameter of theresource block assignment.

According to an example embodiment, the wireless device may determinethe validation is achieved in response to cyclic redundancy check paritybits of the downlink control information being scrambled with the radionetwork temporary identifier of the semi-persistent CSI reporting. Thewireless device may determine the validation is achieved in response tothe hybrid automatic repeat request process number being set to thefirst value. The wireless device may determine the validation isachieved in response to the redundancy version being set to the secondvalue. The wireless device may determine the validation is achieved inresponse to a value of modulation and coding scheme, of the downlinkcontrol information, not being set to a third value. The wireless devicemay determine the validation is achieved in response to a parameter of aresource block assignment, of the downlink control information, notbeing set to a fourth value. According to an example embodiment, thethird value may be a predefined value comprising a bit string with bitsset to “1”. According to an example embodiment, the fourth value may bea predefined value comprising a bit string with bits set to “1”.According to an example embodiment, the fourth value may be a predefinedvalue comprising a bit string with bits set to “0”.

According to an example embodiment, the base station may receive one ormore radio resource control messages. The one or more radio resourcecontrol messages may comprise the radio network temporary identifier ofthe semi-persistent CSI reporting. The one or more radio resourcecontrol messages may comprise configuration parameters of a plurality ofsemi-persistent CSI reporting comprising the semi-persistent CSIreporting. According to an example embodiment, the one or more radioresource control messages may comprise a second radio network temporaryidentifier of a semi-persistent downlink scheduling or a configureduplink grant. The second radio network temporary identifier may bedifferent from the radio network temporary identifier of thesemi-persistent CSI reporting. According to an example embodiment, theone or more radio resource control messages may comprise a third radionetwork temporary identifier of a dynamic downlink assignment or adynamic uplink grant. The third radio network temporary identifier maybe different from the radio network temporary identifier of thesemi-persistent CSI reporting. According to an example embodiment, theconfiguration parameters of the semi-persistent CSI reporting of theplurality of semi-persistent CSI reporting may comprise radio resourcesof one or more reference signals. The configuration parameters of thesemi-persistent CSI reporting of the plurality of semi-persistent CSIreporting may comprise report quantity indication. The configurationparameters of the semi-persistent CSI reporting of the plurality ofsemi-persistent CSI reporting may comprise a report periodicity. Theconfiguration parameters of the semi-persistent CSI reporting of theplurality of semi-persistent CSI reporting may comprise frequencygranularity for CQI and PMI. The configuration parameters of thesemi-persistent CSI reporting of the plurality of semi-persistent CSIreporting may comprise measurement restriction configurations. Accordingto an example embodiment, the report quantity indication may indicatewhich one or more of CQI/PMI/CRI/RI/L1-RSRP values are transmitted inthe semi-persistent CSI report. According to an example embodiment, thewireless device may transmit the semi-persistent CSI report with thereport periodicity. The semi-persistent CSI report may comprise one ormore CQI/PMI/CRI/RI/L1-RSRP values according to the report quantityindication.

FIG. 52 is a flow diagram of an aspect of an embodiment of the presentdisclosure. At 5210, a downlink control information may be received. Thedownlink control information may comprise a power control command of anuplink shared channel. The downlink control information may comprise achannel state information (CSI) request field. The downlink controlinformation may comprise a hybrid automatic repeat request processnumber. The downlink control information may comprise a redundancyversion. At 5220, the downlink control information for an activation ofa semi-persistent CSI reporting may be validated based on a radionetwork temporary identifier of the semi-persistent CSI reporting. Thedownlink control information for an activation of a semi-persistent CSIreporting may be validated based on the hybrid automatic repeat requestprocess number being set to a first value. The downlink controlinformation for an activation of a semi-persistent CSI reporting may bevalidated based on the redundancy version being set to a second value.At 5230, the semi-persistent CSI reporting indicated by the CSI requestfield may be activated in response to the validation of the downlinkcontrol information being achieved. At 5240, in response to activatingsemi-persistent CSI reporting, a semi-persistent CSI report may betransmitted via the uplink shared channel with a transmission powerdetermined based on the power control command.

FIG. 53 is a flow diagram of an aspect of an embodiment of the presentdisclosure. At 5310, a base station may transmit a downlink controlinformation to a wireless device. The downlink control information maycomprise a power control command of an uplink shared channel. Thedownlink control information may comprise a channel state information(CSI) request field. The downlink control information may comprise ahybrid automatic repeat request process number. The downlink controlinformation may comprise a redundancy version. At 5320, in response tothe transmitting, a semi-persistent CSI reporting may be activated forthe wireless device. The activation may be based on a radio networktemporary identifier of the semi-persistent CSI reporting. Theactivation may be based on the hybrid automatic repeat request processnumber being set to a first value. The activation may be based on theredundancy version being set to a second value. At 5330, the wirelessdevice may receive, for the activated semi-persistent CSI reporting, asemi-persistent CSI report via the uplink shared channel.

According to an example embodiment, the base station may activate thesemi-persistent CSI reporting in response to cyclic redundancy checkparity bits of the downlink control information being scrambled with theradio network temporary identifier of the semi-persistent CSI reporting.The base station may activate the semi-persistent CSI reporting inresponse to the hybrid automatic repeat request process number being setto the first value. The base station may activate the semi-persistentCSI reporting in response to the redundancy version being set to thesecond value. According to an example embodiment, the semi-persistentCSI report may comprise a channel quality indicator (CQI). Thesemi-persistent CSI report may comprise a precoding matrix indicator(PMI). The semi-persistent CSI report may comprise a channel stateinformation reference signal resource indicator (CRI). Thesemi-persistent CSI report may comprise a layer indicator (LI). Thesemi-persistent CSI report may comprise a rank indicator (RI). Thesemi-persistent CSI report may comprise a layer 1 reference signalreceived power (L1-RSRP). According to an example embodiment, the basestation may receive the semi-persistent CSI report with a reportperiodicity of the activated semi-persistent CSI reporting. According toan example embodiment, the first value may be a predefined value,comprising a bit string with bits set to “0”. According to an exampleembodiment, the second value may be a predefined value, comprising a bitstring with bits set to “0”. According to an example embodiment, thedownlink control information may comprise a new data indicator field.

According to an example embodiment, the downlink control information maycomprise a value indicating a modulation and coding scheme. The downlinkcontrol information may comprise a parameter of resource blockassignment on the uplink shared channel. According to an exampleembodiment, the base station may activate the semi-persistent CSIreporting further in response to the value indicating the modulation andcoding scheme not being set to a third value. The base station mayactivate the semi-persistent CSI reporting further in response to theparameter of the resource block assignment not being set to a fourthvalue. According to an example embodiment, the base station may receivethe semi-persistent CSI report via one or more resource blocks of theuplink shared channel. The one or more resource blocks may be indicatedby the parameter of the resource block assignment.

According to an example embodiment, the base station may activate thesemi-persistent CSI reporting in response to cyclic redundancy checkparity bits of the downlink control information being scrambled with theradio network temporary identifier of the semi-persistent CSI reporting.The base station may activate the semi-persistent CSI reporting inresponse to the hybrid automatic repeat request process number being setto the first value. The base station may activate the semi-persistentCSI reporting in response to the redundancy version being set to thesecond value. The base station may activate the semi-persistent CSIreporting in response to a value of modulation and coding scheme, of thedownlink control information, not being set to a third value. The basestation may activate the semi-persistent CSI reporting in response to aparameter of a resource block assignment, of the downlink controlinformation, not being set to a fourth value. According to an exampleembodiment, the third value may be a predefined value comprising a bitstring with bits set to “1”. According to an example embodiment, thefourth value may be a predefined value, comprising a bit string withbits set to “1”. According to an example embodiment, the fourth valuemay be a predefined value, comprising a bit string with bits set to “0”.

According to an example embodiment, the wireless device may transmit oneor more radio resource control messages. The one or more radio resourcecontrol messages may comprise the radio network temporary identifier ofthe semi-persistent CSI reporting. The one or more radio resourcecontrol messages may comprise configuration parameters of a plurality ofsemi-persistent CSI reporting comprising the semi-persistent CSIreporting. According to an example embodiment, the one or more radioresource control messages may comprise a second radio network temporaryidentifier of a semi-persistent downlink scheduling or a configureduplink grant. The second radio network temporary identifier may bedifferent from the radio network temporary identifier of thesemi-persistent CSI reporting. According to an example embodiment, theone or more radio resource control messages may comprise a third radionetwork temporary identifier of a dynamic downlink assignment or adynamic uplink grant. The third radio network temporary identifier maybe different from the radio network temporary identifier of thesemi-persistent CSI reporting. According to an example embodiment, theconfiguration parameters of the semi-persistent CSI reporting of theplurality of semi-persistent CSI reporting may comprise radio resourcesof one or more reference signals. The configuration parameters of thesemi-persistent CSI reporting of the plurality of semi-persistent CSIreporting may comprise report quantity indication. The configurationparameters of the semi-persistent CSI reporting of the plurality ofsemi-persistent CSI reporting may comprise a report periodicity. Theconfiguration parameters of the semi-persistent CSI reporting of theplurality of semi-persistent CSI reporting may comprise frequencygranularity for CQI and PMI. The configuration parameters of thesemi-persistent CSI reporting of the plurality of semi-persistent CSIreporting may comprise measurement restriction configurations. Accordingto an example embodiment, the report quantity indication may indicatewhich one or more of CQI/PMI/CRI/RI/L1-RSRP values are transmitted inthe semi-persistent CSI report. According to an example embodiment, thebase station may receive the semi-persistent CSI report with the reportperiodicity. The semi-persistent CSI report may comprise one or moreCQI/PMI/CRI/RI/L1-RSRP values according to the report quantityindication.

FIG. 54 is a flow diagram of an aspect of an embodiment of the presentdisclosure. At 5410, a wireless device may receive a downlink controlinformation from a base station. The downlink control information maycomprise a power control command of an uplink shared channel. Thedownlink control information may comprise a channel state information(CSI) request field. The downlink control information may comprise ahybrid automatic repeat request process number. The downlink controlinformation may comprise a redundancy version. At 5420, the downlinkcontrol information for an activation of a semi-persistent CSI reportingmay be validated. The validation may be based on a radio networktemporary identifier of the semi-persistent CSI reporting. Thevalidation may be based on the hybrid automatic repeat request processnumber. The validation may be based on the redundancy version. At 5430,the semi-persistent CSI reporting indicated by the CSI request field maybe activated in response to the validation being achieved. At 5440,based on the activated semi-persistent CSI reporting, a semi-persistentCSI report may be transmitted via the uplink shared channel with atransmission power determined based on the power control command.

According to an example embodiment, the wireless device may determinethe validation is achieved in response to cyclic redundancy check paritybits of the downlink control information being scrambled with the radionetwork temporary identifier of the semi-persistent CSI reporting. Thewireless device may determine the validation is achieved in response tothe hybrid automatic repeat request process number being set to a firstvalue. The wireless device may determine the validation is achieved inresponse to the redundancy version being set to a second value.According to an example embodiment, the first value may be a predefinedvalue, comprising a bit string with bits set to “0”. According to anexample embodiment, the second value may be a predefined value,comprising a bit string with bits set to “0”.

FIG. 55 is a flow diagram of an aspect of an embodiment of the presentdisclosure. At 5510, a wireless device may transmit a semi-persistentCSI report for a semi-persistent CSI reporting. At 5520, a downlinkcontrol information may be received. The downlink control informationmay comprise a channel state information (CSI) request field. Thedownlink control information may comprise a hybrid automatic repeatrequest process number. The downlink control information may comprise avalue of modulation and coding scheme. The downlink control informationmay comprise a parameter of resource block assignment. The downlinkcontrol information may comprise a redundancy version. At 5530, thedownlink control information for a deactivation of the semi-persistentCSI reporting may be validated. The validation may be based on a radionetwork temporary identifier of the semi-persistent CSI reporting. Thevalidation may be based on the hybrid automatic repeat request processnumber. The validation may be based on the redundancy version. Thevalidation may be based on the parameter of resource block assignment.The validation may be based on the value of modulation and codingscheme. At 5540, the semi-persistent CSI reporting indicated by the CSIrequest field may be deactivated in response to the validation beingachieved. At 5550, the transmitting of the semi-persistent CSI reportvia an uplink shared channel may be stopped.

According to an example embodiment, the wireless device may determinethe validation is achieved in response to cyclic redundancy check paritybits of the downlink control information being scrambled with the radionetwork temporary identifier. The wireless device may determine thevalidation is achieved in response to the hybrid automatic repeatrequest process number being set to a first value. The wireless devicemay determine the validation is achieved in response to the redundancyversion being set to a second value. The wireless device may determinethe validation is achieved in response to the value of modulation andcoding scheme being set to a third value. The wireless device maydetermine the validation is achieved in response to the parameter of theresource block assignment being set to a fourth value. According to anexample embodiment, the first value may be a predefined value comprisinga bit string with bits set to “0”. According to an example embodiment,the second value may be a predefined value, comprising a bit string withbits set to “0”. According to an example embodiment, the third value maybe a predefined value, comprising a bit string with bits set to “1”.According to an example embodiment, the fourth value may be a predefinedvalue, comprising a bit string with bits set to “1”. According to anexample embodiment, the fourth value may be a predefined value,comprising a bit string with bits set to “0”.

FIG. 56 is a flow diagram of an aspect of an embodiment of the presentdisclosure. At 5610, a wireless device may receive one or more messagesfrom a base station. The one or more messages may comprise parameters ofa plurality of semi-persistent channel state information (SP CSI)reporting. The one or more messages may comprise a SP CSI radio networktemporary identifier. At 5620, a downlink control information may bereceived. The downlink control information may comprise a power controlcommand of an uplink shared channel. The downlink control informationmay comprise a channel state information request filed indicating a SPCSI reporting of the plurality of SP CSI reporting. The downlink controlinformation may comprise a hybrid automatic repeat request processnumber. The downlink control information may comprise a redundancyversion. At 5630, a validation of the downlink control information foran activation of the SP CSI reporting may be performed based on the SPCSI radio network temporary identifier. The validation of the downlinkcontrol information for an activation of the SP CSI reporting may beperformed based on the hybrid automatic repeat request process number.The validation of the downlink control information for an activation ofthe SP CSI reporting may be performed based on the redundancy version.At 5640, in response to the validation being achieved and based on theSP CSI reporting, a SP CSI report may be transmitted via the uplinkshared channel with a transmission power determined based on the powercontrol command.

According to an example embodiment, the wireless device may determinethe validation is achieved in response to cyclic redundancy check paritybits of the downlink control information being scrambled with the SP CSIradio network temporary identifier. The wireless device may determinethe validation is achieved in response to the hybrid automatic repeatrequest process number being set to a first value. The wireless devicemay determine the validation is achieved in response to the redundancyversion being set to a second value. According to an example embodiment,the first value may be a predefined value, comprising a bit string withbits set to “0”. According to an example embodiment, the second valuemay be a predefined value, comprising a bit string with bits set to “0”.

FIG. 57 is a flow diagram of an aspect of an embodiment of the presentdisclosure. At 5710, a wireless device may receive a downlink controlinformation from a base station via a downlink control channel. At 5720,the downlink control information for an activation of a semi-persistentCSI reporting may be validated. The validation may be based on a radionetwork temporary identifier of the semi-persistent CSI reporting. Thevalidation may be based on a hybrid automatic repeat request processnumber of the downlink control information. The validation may be basedon a redundancy version of the downlink control information. At 5730,the semi-persistent CSI reporting may be activated in response to thevalidation being achieved.

According to an example embodiment, for the activated semi-persistentCSI reporting, a semi-persistent CSI report may be transmitted with atransmission power determined based on a power control command of thedownlink control information. According to an example embodiment, forthe activated semi-persistent CSI reporting, a semi-persistent CSIreport may be transmitted via an uplink shared channel. According to anexample embodiment, the semi-persistent CSI report may be transmittedwith a transmission power determined based on a power control command ofthe downlink control information. According to an example embodiment,the wireless device may determine the validation is achieved in responseto cyclic redundancy check parity bits of the downlink controlinformation being scrambled with the radio network temporary identifierof the semi-persistent CSI reporting. The wireless device may determinethe validation is achieved in response to the hybrid automatic repeatrequest process number being set to a first value. The wireless devicemay determine the validation is achieved in response to the redundancyversion being set to a second value. According to an example embodiment,the first value may be a predefined value, comprising a bit string withbits set to “0”. According to an example embodiment, the second valuemay be a predefined value, comprising a bit string with bits set to “0”.

FIG. 58 is a flow diagram of an aspect of an embodiment of the presentdisclosure. At 5810, a wireless device may initiate a beam failurerecovery procedure in response to detecting a first number of beamfailure instances. At 5820, a beam failure recovery timer may be startedwith a first timer value. At 5830, a first reference signal may beselected in response to an expiry of the beam failure recovery timer. At5840, a first preamble associated with the first reference signal may betransmitted. At 5850, during a response window and in response totransmitting the first preamble, a downlink control channel for adownlink control information may be monitored. At 5860, a preambletransmission counter may be incremented, from a value of the preambletransmission counter before the expiry of the beam failure recoverytimer. The preamble transmission counter incrementing may be in responseto not receiving the downlink control information during the responsewindow. At 5870, in response to the preamble transmission counterindicating a second number equal to or less than a third number forpreamble transmissions, a second preamble for the beam failure recoveryprocedure may be transmitted.

According to an example embodiment, the beam failure recovery proceduremay be unsuccessfully completing in response to the preambletransmission counter indicating the second number greater than the thirdnumber for preamble transmissions. According to an example embodiment,the beam failure recovery procedure may be successfully completing inresponse to receiving the downlink control information during themonitoring. According to an example embodiment, the initiating the beamfailure recovery procedure may comprise setting the preambletransmission counter to an initial value. According to an exampleembodiment, the initial value may be 1. According to an exampleembodiment, the wireless device may increment the preamble transmissioncounter in response to the preamble transmission counter indicating thesecond number equal to or less than the third number for preambletransmissions.

According to an example embodiment, one or more radio resource controlmessages may be received. The one or more radio resource controlmessages may comprise configuration parameters of the beam failurerecovery procedure. The configuration parameters may comprise a firstplurality of reference signals. The configuration parameters maycomprise the first timer value. The configuration parameters maycomprise the first number. The configuration parameters may comprise thethird number. According to an example embodiment, the wireless devicemay detect the first number of beam failure instances based on the firstplurality of reference signals. A beam failure instance of the firstnumber of beam failure instances may occur in response to radio linkquality of the first plurality of reference signals being worse than afirst threshold. According to an example embodiment, the radio linkquality may comprise a value of block error rate (BLER).

According to an example embodiment, first information may be indicatedto a radio resource control layer of the wireless device in response tothe preamble transmission counter indicating the second number greaterthan the third number for preamble transmissions. According to anexample embodiment, the first information may indicate a random accessproblem. The first information may indicate the preamble transmissioncounter indicating the second number greater than the third number forpreamble transmissions. The first information may indicate a failure ofthe beam failure recovery procedure. The first information may indicateout of synchronization. According to an example embodiment, the wirelessdevice may transmit a radio link failure report to the base station. Theradio link failure report may comprise the first information.

According to an example embodiment, the wireless device may select asecond reference signal during the beam failure recovery timer beingrunning. According to an example embodiment, the wireless device maytransmit a third preamble being associated with the second referencesignal. According to an example embodiment, the wireless device maymonitor, in response to transmitting the third preamble and during afirst response window, a first downlink control channel for a firstdownlink control information. According to an example embodiment, thewireless device may increment the preamble transmission counter inresponse to not receiving the first downlink control information duringthe first response window.

According to an example embodiment, the third preamble being associatedwith the second reference signal may be indicated by one or more beamfailure configuration parameters in a radio resource control message.According to an example embodiment, the wireless device may monitor thefirst downlink control channel in a control resource set for the beamfailure recovery procedure. According to an example embodiment, thefirst downlink control information may be in response to the thirdpreamble for the beam failure recovery procedure.

According to an example embodiment, the wireless device may select thesecond reference signal with a radio link quality greater than a secondthreshold, from a plurality of reference signals. According to anexample embodiment, the radio link quality may comprise a value ofreference signal received power (RSRP). According to an exampleembodiment, the plurality of reference signals may be configured in aradio resource control message.

FIG. 59 is a flow diagram of an aspect of an embodiment of the presentdisclosure. At 5910, a beam failure recovery procedure may be initiatedin response to detecting a number of beam failure instances. At 5920, abeam failure recovery timer may be started with a timer value. At 5930,a first reference signal may be selected in response to an expiry of thebeam failure recovery timer. At 5940, a first preamble associated withthe first reference signal may be transmitted. At 5950, a downlinkcontrol channel for a downlink control information may be monitoredduring a response window and in response to transmitting the firstpreamble. At 5960, a preamble transmission counter may be incremented,from a value of the preamble transmission counter before the expiry ofthe beam failure recovery timer, in response to not receiving thedownlink control information during the response window. At 5970, inresponse to the preamble transmission counter indicating a first numberequal to or less than a second number for preamble transmissions, asecond preamble for the beam failure recovery procedure may betransmitted.

FIG. 60 is a flow diagram of an aspect of an embodiment of the presentdisclosure. At 6010, a beam failure recovery timer may be started with atimer value in response to initiating a beam failure recovery procedure.At 6020, a first preamble may be transmitted during the beam failurerecovery timer being running. At 6030, a preamble transmission countermay be incremented, in response to not receiving a first response forthe first preamble during a first response window. At 6040, a secondpreamble may be transmitted in response to an expiry of the beam failurerecovery timer. At 6050, a downlink control channel may be monitored fora second response, in response to transmitting the second preamble andduring a second response window. At 6060, the preamble transmissioncounter may be incremented, from a value of the preamble transmissioncounter before the expiry of the beam failure recovery timer, inresponse to not receiving the second response for the second preamble.

According to an example embodiment, in response to the preambletransmission counter indicating a first number equal to or less than asecond number for preamble transmissions, a third preamble for the beamfailure recovery procedure may be transmitted. According to an exampleembodiment, the beam failure recovery procedure may be unsuccessfullycompleted in response to the preamble transmission counter indicating afirst number greater than a second number for preamble transmissions.According to an example embodiment, the beam failure recovery proceduremay be completed in response to receiving the first response. Accordingto an example embodiment, the beam failure recovery procedure may besuccessfully completed in response to receiving the second response.

FIG. 61 is a flow diagram of an aspect of an embodiment of the presentdisclosure. At 6110, a beam failure recovery procedure may be initiatedin response to detecting beam failure instances. At 6120, a beam failurerecovery timer may be started with a timer value. At 6130, a preambletransmission counter may be incremented to a first value in response tonot receiving a first response for a transmission of a first preambleduring a first response window. At 6140, a second preamble may betransmitted in response to an expiry of the beam failure recovery timer.At 6150, during a second response window, a downlink control channel maybe monitored for a second response to the second preamble. At 6160, thepreamble transmission counter may be incremented from the first value inresponse to not receiving the second response during the second responsewindow.

FIG. 62 is a flow diagram of an aspect of an embodiment of the presentdisclosure. At 6210, a beam failure recovery timer may be started with atimer value in response to initiating a beam failure recovery procedure.At 6220, a first preamble may be transmitted during the beam failurerecovery timer being running. At 6230, a preamble transmission countermay be incremented to a first value in response to not receiving a firstresponse to the first preamble during a first response window. At 6240,a second preamble may be transmitted in response to an expiry of thebeam failure recovery timer. At 6250, during a second response window, asecond downlink control channel may be monitored for a second responseto the second preamble. At 6260, the preamble transmission counter maybe incremented from the first value in response to not receiving thesecond response during the second response window. At 6270, a radio linkfailure report may be transmitted in response to the preambletransmission counter indicating a first number greater than a secondnumber for preamble transmissions. The radio link failure report maycomprise one or more parameters indicating a random access problem or afailure of the beam failure recovery procedure.

FIG. 63 is a flow diagram of an aspect of an embodiment of the presentdisclosure. At 6310, a wireless device may receive a medium accesscontrol (MAC) control element (CE) identified by a MAC subheader. The inthe MAC CE may comprise a first field associated with a first cell of aplurality of cells. The first field being set to a first value mayindicate a command of activation/deactivation of SP CSI reporting on thefirst cell is present. The in the MAC CE may comprise a semi-persistentchannel state information (SP CSI) reporting activation/deactivationindicator. The MAC CE may comprise a SP CSI report trigger fieldindicating a SP CSI reporting of a plurality of SP CSI reporting on thefirst cell. At 6320, in response to the SP CSI reportingactivation/deactivation indicator indicating an activation of the SP CSIreporting on the first cell, a SP CSI report for the first cell may betransmitted via an uplink control channel.

According to an example embodiment, the MAC subheader may comprise alength field indicating a size of the MAC CE. The MAC subheader maycomprise a logical channel identifier indicating the MAC CE is foractivation/deactivation of the SP CSI reporting. According to an exampleembodiment, the MAC CE may have a fixed size. According to an exampleembodiment, the first value may be 1. According to an exampleembodiment, the plurality of cells may comprise a primary cell and oneor more secondary cells. According to an example embodiment, the firstcell, associated with the first field, may be indicated in a radioresource control message. According to an example embodiment, the firstcell, associated with the first field, may be identified by a cell indexof the first cell, wherein the cell index determines a location of thefirst field in the MAC CE. According to an example embodiment, the SPCSI reporting activation/deactivation indicator may comprise a bit.According to an example embodiment, the wireless device may transmit theSP CSI report with a report periodicity indicated by one or moreparameters of the SP CSI reporting. According to an example embodiment,the wireless device may transmit the SP CSI report via the uplinkcontrol channel indicated by one or more parameters of the SP CSIreporting. According to an example embodiment, one or more radioresource control messages may be received. The one or more radioresource control messages may comprise configuration parameters of theplurality of SP CSI reporting on the plurality of cells. Theconfiguration parameters may indicate one or more channel stateinformation reference signal resource configurations. The configurationparameters may indicate one or more channel state information reportquantity indicators. The configuration parameters may indicate a reportperiodicity. The configuration parameters may indicate one or moreuplink control channel configuration parameters. According to an exampleembodiment, in response to the SP CSI reporting activation/deactivationindicator indicating a deactivation of the SP CSI reporting on the firstcell, a transmission of the SP CSI report for the first cell via theuplink control channel may be stopped. According to an exampleembodiment, the SP CSI reporting activation/deactivation indicator maycomprise a bit.

According to an example embodiment, the MAC CE may comprise a referencesignal resource indicator indicating at least one of a plurality of RSsof the first cell. According to an example embodiment, the wirelessdevice may transmit the SP CSI report measured on the one of theplurality of RSs of the first cell.

According to an example embodiment, the MAC CE may comprise a secondfield associated with a second cell of the plurality of cells. Thesecond field being set to a second value may indicate a command ofactivation/deactivation of SP CSI reporting on the second cell isabsent. According to an example embodiment, the second value may be 0.According to an example embodiment, the second cell, association withthe second field, may be indicated in a radio resource control message.According to an example embodiment, the second cell, association withthe second field, may be identified by a cell index of the second cell.The cell index may determine a location of the second field in the MACCE. According to an example embodiment, a state of SP CSI reporting onthe second cell may be maintained in response to the second fieldassociated with the second cell indicating the command ofactivation/deactivation of SP CSI reporting on the second cell isabsent.

FIG. 64 is a flow diagram of an aspect of an embodiment of the presentdisclosure. At 6410, a wireless device may receive one or more messagesfrom a base station. The one or more messages may comprise one or morefirst configuration parameters of a plurality of cells. The one or moremessages may comprise one or more second configuration parameters of aplurality of SP CSI reporting. At 6420, a medium access control (MAC)control element (CE) identified by a MAC subheader may be received. TheMAC CE may comprise a first field associated with a first cell of theplurality of cells. The first field being set to a first value mayindicate a command of activation/deactivation of SP CSI reporting on thefirst cell is present. The MAC CE may comprise a semi-persistent channelstate information (SP CSI) reporting activation/deactivation indicator.The MAC CE may comprise a SP CSI report trigger field indicating a SPCSI reporting of a plurality of SP CSI reporting on the first cell. At6430, in response to the SP CSI reporting activation/deactivationindicator indicating an activation of the SP CSI reporting on the firstcell, a SP CSI report for the first cell may be transmitted via anuplink control channel.

According to an example embodiment, the MAC subheader may comprise alength field indicating a size of the MAC CE. The MAC subheader maycomprise a logical channel identifier indicating the MAC CE is foractivation/deactivation of the SP CSI reporting. According to an exampleembodiment, the MAC CE may comprise a second field associated with asecond cell of the plurality of cells. The second field may be set to asecond value indicates a command of activation/deactivation of SP CSIreporting on the second cell is absent. According to an exampleembodiment, a state of SP CSI reporting on the second cell may bemaintained in response to the second field associated with the secondcell indicating the command of activation/deactivation of SP CSIreporting on the second cell is absent.

In this disclosure, “a” and “an” and similar phrases are to beinterpreted as “at least one” or “one or more.” Similarly, any term thatends with the suffix “(s)” is to be interpreted as “at least one” or“one or more.” In this disclosure, the term “may” is to be interpretedas “may, for example.” In other words, the term “may” is indicative thatthe phrase following the term “may” is an example of one of a multitudeof suitable possibilities that may, or may not, be employed to one ormore of the various embodiments. If A and B are sets and every elementof A is also an element of B, A is called a subset of B. In thisspecification, only non-empty sets and subsets are considered. Forexample, possible subsets of B={cell1, cell2} are: {cell1}, {cell2}, and{cell1, cell2}. The phrase “based on” is indicative that the phrasefollowing the term “based on” is an example of one of a multitude ofsuitable possibilities that may, or may not, be employed to one or moreof the various embodiments. The phrase “in response to” is indicativethat the phrase following the phrase “in response to” is an example ofone of a multitude of suitable possibilities that may, or may not, beemployed to one or more of the various embodiments. The terms“including” and “comprising” should be interpreted as meaning“including, but not limited to.”

In this disclosure and the claims, differentiating terms like “first,”“second,” “third,” identify separate elements without implying anordering of the elements or functionality of the elements.Differentiating terms may be replaced with other differentiating termswhen describing an embodiment.

In this disclosure, various embodiments are disclosed. Limitations,features, and/or elements from the disclosed example embodiments may becombined to create further embodiments within the scope of thedisclosure.

In this disclosure, parameters (Information elements: IEs) may compriseone or more objects, and each of those objects may comprise one or moreother objects. For example, if parameter (IE) N comprises parameter (IE)M, and parameter (IE) M comprises parameter (IE) K, and parameter (IE) Kcomprises parameter (information element) J, then, for example, Ncomprises K, and N comprises J. In an example embodiment, when one ormore messages comprise a plurality of parameters, it implies that aparameter in the plurality of parameters is in at least one of the oneor more messages, but does not have to be in each of the one or moremessages.

Furthermore, many features presented above are described as beingoptional through the use of “may” or the use of parentheses. For thesake of brevity and legibility, the present disclosure does notexplicitly recite each and every permutation that may be obtained bychoosing from the set of optional features. However, the presentdisclosure is to be interpreted as explicitly disclosing all suchpermutations. For example, a system described as having three optionalfeatures may be embodied in seven different ways, namely with just oneof the three possible features, with any two of the three possiblefeatures or with all three of the three possible features.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an isolatableelement that performs a defined function and has a defined interface toother elements. The modules described in this disclosure may beimplemented in hardware, software in combination with hardware,firmware, wetware (i.e. hardware with a biological element) or acombination thereof, all of which are behaviorally equivalent. Forexample, modules may be implemented as a software routine written in acomputer language configured to be executed by a hardware machine (suchas C, C++, Fortran, Java, Basic, Matlab or the like) or amodeling/simulation program such as Simulink, Stateflow, GNU Octave, orLabVIEWMathScript. Additionally, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers and microprocessors are programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDsare often programmed using hardware description languages (HDL) such asVHSIC hardware description language (VHDL) or Verilog that configureconnections between internal hardware modules with lesser functionalityon a programmable device. Finally, it needs to be emphasized that theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the scope. In fact, after reading the abovedescription, it will be apparent to one skilled in the relevant art(s)how to implement alternative embodiments. Thus, the present embodimentsshould not be limited by any of the above described exemplaryembodiments.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112. Claims that do not expressly include the phrase “means for”or “step for” are not to be interpreted under 35 U.S.C. 112.

What is claimed is:
 1. A method comprising: receiving, by a wirelessdevice from a base station, a downlink control information comprising: apower control command of an uplink shared channel; a channel stateinformation (CSI) request field; a hybrid automatic repeat requestprocess number; and a redundancy version; performing a validation of thedownlink control information for an activation of a semi-persistent CSIreporting based on: a radio network temporary identifier of thesemi-persistent CSI reporting; the hybrid automatic repeat requestprocess number being set to a first value; and the redundancy versionbeing set to a second value; activating the semi-persistent CSIreporting indicated by the CSI request field in response to thevalidation being achieved; and transmitting, based on the activatedsemi-persistent CSI reporting, a semi-persistent CSI report via theuplink shared channel with a transmission power determined based on thepower control command, wherein the power control command is not used toperform the validation.
 2. The method of claim 1, wherein the wirelessdevice determines the validation is achieved in response to: cyclicredundancy check parity bits of the downlink control information beingscrambled with the radio network temporary identifier of thesemi-persistent CSI reporting; the hybrid automatic repeat requestprocess number being set to the first value; and the redundancy versionbeing set to the second value.
 3. The method of claim 1, wherein thesemi-persistent CSI report comprises at least one or more values of: achannel quality indicator (CQI); a precoding matrix indicator (PMI); achannel state information reference signal resource indicator (CRI); alayer indicator (LI); a rank indicator (RI); and a layer 1 referencesignal received power (L1-RSRP).
 4. The method of claim 1, wherein thewireless device transmits the semi-persistent CSI report with a reportperiodicity of the activated semi-persistent CSI reporting.
 5. Themethod of claim 1, wherein the first value is a predefined valuecomprising a bit string with bits set to “0”.
 6. The method of claim 1,wherein the second value is a predefined value comprising a bit stringwith bits set to “0”.
 7. The method of claim 1, wherein the downlinkcontrol information further comprises a new data indicator field.
 8. Themethod of claim 7, wherein the wireless device validates the downlinkcontrol information regardless of a value of the new data indicatorfield and a value of the power control command.
 9. The method of claim1, further comprising skipping the downlink control information by notapplying the downlink control information in response to the validationnot being achieved.
 10. The method of claim 9, wherein the validation isnot achieved in response to at least one of: cyclic redundancy checkparity bits of the downlink control information not being scrambled withthe radio network temporary identifier of the semi-persistent CSIreporting; the hybrid automatic repeat request process number not beingset to the first value; and the redundancy version not being set to thesecond value.
 11. The method of claim 1, wherein the downlink controlinformation further comprises: a value indicating a modulation andcoding scheme; and a parameter of resource block assignment on theuplink shared channel.
 12. The method of claim 11, wherein the wirelessdevice determines the validation is achieved further in response to: thevalue indicating the modulation and coding scheme not being set to athird value; and the parameter of the resource block assignment notbeing set to a fourth value.
 13. The method of claim 11, wherein thewireless device transmits the semi-persistent CSI report via one or moreresource blocks of the uplink shared channel, wherein the one or moreresource blocks are indicated by the parameter of the resource blockassignment.
 14. The method of claim 1, wherein the wireless devicedetermines the validation is achieved in response to: cyclic redundancycheck parity bits of the downlink control information being scrambledwith the radio network temporary identifier of the semi-persistent CSIreporting; the hybrid automatic repeat request process number being setto the first value; the redundancy version being set to the secondvalue; a value of a modulation and coding scheme, of the downlinkcontrol information, not being set to a third value; and a parameter ofa resource block assignment, of the downlink control information, notbeing set to a fourth value.
 15. The method of claim 14, wherein thethird value is a predefined value comprising a bit string with bits setto “1”.
 16. The method of claim 14, wherein the fourth value is apredefined value comprising a bit string with bits set to “1”.
 17. Themethod of claim 14, wherein the fourth value is a predefined valuecomprising a bit string with bits set to “0”.
 18. The method of claim 1,further comprising receiving, from the base station, one or more radioresource control messages comprising: the radio network temporaryidentifier of the semi-persistent CSI reporting; and configurationparameters of a plurality of semi-persistent CSI reporting comprisingthe semi-persistent CSI reporting.
 19. The method of claim 18, whereinthe one or more radio resource control messages further comprise asecond radio network temporary identifier of a semi-persistent downlinkscheduling or a configured uplink grant, wherein the second radionetwork temporary identifier is different from the radio networktemporary identifier of the semi-persistent CSI reporting.
 20. Themethod of claim 18, wherein the one or more radio resource controlmessages further comprise a third radio network temporary identifier ofa dynamic downlink assignment or a dynamic uplink grant, wherein thethird radio network temporary identifier is different from the radionetwork temporary identifier of the semi-persistent CSI reporting.